Zero-Trust Physics: tool descriptions scored com.zerotrustphysics/verifier

tools/list taken: 2026-11-02 (UTC)
From: Official MCP Registry
Connected to: https://mcp.zerotrustphysics.com/mcp
Homepage: zerotrustphysics.com
Scoring rules: v2
Removal: support@forecall.dev

Scores, issues and names only

This page shows how Zero-Trust Physics (com.zerotrustphysics/verifier)'s tool descriptions scored, the issues found and the names of its tools and parameters. The descriptions are the server's own: read them where the copy came from.

Forecall asked the URL this server lists in the official MCP Registry for its tools/list once, on the date above, without calling any tool. The server may have changed since.

servers/com.zerotrustphysics/verifier

Average score: 55.2 / 100Cloudy
Tools: 18
Near-identical descriptions: 3

Across the server

Major
11 tools repeat the same note (42 words). Say it once in the server's instructions, and let each description say what only that tool does. The note does not count toward the tools' scores.repeated_note

Tools whose descriptions are nearly the same

3 of 3 pairs shown, highest description similarity first.
Tool	Tool	Description similarity	Name similarity
list_cards	list_solvers	0.92	0.33
verify_tape	verify_solution	0.72	0.33
describe_card	describe_solver	0.65	0.33

Tools

cite

39 / 100Rain

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 12 / 25
Return value: 0 / 15
Constraints and side effects: 10 / 10
Examples: 0 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context
Minor
Arguments without a description: card.param_no_description
Minor
String arguments with no constraint or example: card.loose_string_param
Minor
No `required` list, so every argument is optional.no_required
Minor
Says nothing about what it returns.no_return_info

verify_step

44 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 15 / 25
Return value: 0 / 15
Constraints and side effects: 7 / 10
Examples: 5 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context
Minor
Arguments without a description: from.request, from.run_seal, from.coupling.param_no_description
Minor
String arguments with no constraint or example: from.coupling.loose_string_param
Minor
Says nothing about what it returns.no_return_info

verify_solution

48 / 100Cloudy

Purpose: 17 / 20
When to use: 10 / 20
Arguments: 4 / 25
Return value: 0 / 15
Constraints and side effects: 7 / 10
Examples: 10 / 10

Major
Arguments without a description: engine_version, outcome, iterations, reject, result, invariants, field_sha384, seal_parts, seal_parts.inputs, seal_parts.engine_version, seal_parts.result, seal_parts.invariants, seal_parts.field_sha384, seal_parts.outcome.param_no_description
Minor
Its description is nearly the same as verify_tape's (similarity 0.72); only the names and schemas tell them apart. Say in this description when to use verify_tape instead.confusable_pair
Minor
String arguments with no constraint or example: engine_version, outcome, seal_parts.inputs, seal_parts.engine_version, seal_parts.result, seal_parts.invariants, seal_parts.field_sha384, seal_parts.outcome.loose_string_param
Minor
No `required` list, so every argument is optional.no_required
Minor
Says nothing about what it returns.no_return_info

validate_series

49 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 15 / 25
Return value: 0 / 15
Constraints and side effects: 7 / 10
Examples: 10 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context
Major
Arguments without a description: run.record_every, run.segments, run.segments[].steps, run.segments[].signed.alg, run.segments[].signed.key, run.segments[].signed.instrument, run.segments[].signed.time, run.segments[].signed.seq, run.segments[].signed.prev, run.segments[].signed.challenge, run.segments[].signed.sig, measurements[].signed.alg, measurements[].signed.key, measurements[].signed.instrument, measurements[].signed.time, measurements[].signed.seq, measurements[].signed.prev, measurements[].signed.challenge, measurements[].signed.sig.param_no_description
Minor
String arguments with no constraint or example: run.segments[].signed.time, measurements[].signed.time.loose_string_param
Minor
Says nothing about what it returns.no_return_info

run_dataset

52 / 100Cloudy

Purpose: 17 / 20
When to use: 5 / 20
Arguments: 13 / 25
Return value: 0 / 15
Constraints and side effects: 7 / 10
Examples: 10 / 10

Major
Arguments without a description: domain, card, store, return.param_no_description
Minor
String arguments with no constraint or example: domain, card.loose_string_param
Minor
Says nothing about what it returns.no_return_info

verify_tape

52 / 100Cloudy

Purpose: 17 / 20
When to use: 10 / 20
Arguments: 8 / 25
Return value: 0 / 15
Constraints and side effects: 7 / 10
Examples: 10 / 10

Major
Arguments without a description: frames, frames[].step, frames[].frame_hex, frames[].link, outcome, steps_landed, reject, final_state, final_residual_conservation_error_hex, max_residual_conservation_error_hex, state_digest.param_no_description
Minor
Its description is nearly the same as verify_solution's (similarity 0.72); only the names and schemas tell them apart. Say in this description when to use verify_solution instead.confusable_pair
Minor
String arguments with no constraint or example: frames[].frame_hex, frames[].link, outcome.loose_string_param
Minor
No `required` list, so every argument is optional.no_required
Minor
Says nothing about what it returns.no_return_info

list_cards

54 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 25 / 25
Return value: 0 / 15
Constraints and side effects: 7 / 10
Examples: 5 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context
Minor
Its description is nearly the same as list_solvers's (similarity 0.92); only the names and schemas tell them apart. Say in this description when to use list_solvers instead.confusable_pair
Minor
Says nothing about what it returns.no_return_info

list_solvers

54 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 25 / 25
Return value: 0 / 15
Constraints and side effects: 7 / 10
Examples: 5 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context
Minor
Its description is nearly the same as list_cards's (similarity 0.92); only the names and schemas tell them apart. Say in this description when to use list_cards instead.confusable_pair
Minor
Says nothing about what it returns.no_return_info

compute_step

56 / 100Cloudy

Purpose: 17 / 20
When to use: 5 / 20
Arguments: 15 / 25
Return value: 7 / 15
Constraints and side effects: 7 / 10
Examples: 5 / 10

Minor
Arguments without a description: from.request, from.run_seal, from.coupling.param_no_description
Minor
String arguments with no constraint or example: from.coupling.loose_string_param

solve

56 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 15 / 25
Return value: 7 / 15
Constraints and side effects: 7 / 10
Examples: 10 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context
Minor
Arguments without a description: from.request, from.run_seal, from.coupling.param_no_description
Minor
String arguments with no constraint or example: from.coupling.loose_string_param

design_run

57 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 20 / 25
Return value: 0 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context
Minor
Says nothing about what it returns.no_return_info

describe_card

61 / 100Cloudy

Purpose: 17 / 20
When to use: 5 / 20
Arguments: 22 / 25
Return value: 0 / 15
Constraints and side effects: 7 / 10
Examples: 10 / 10

Minor
Its description is nearly the same as describe_solver's (similarity 0.65); only the names and schemas tell them apart. Say in this description when to use describe_solver instead.confusable_pair
Minor
Says nothing about what it returns.no_return_info

describe_solver

61 / 100Cloudy

Purpose: 17 / 20
When to use: 5 / 20
Arguments: 22 / 25
Return value: 0 / 15
Constraints and side effects: 7 / 10
Examples: 10 / 10

Minor
Its description is nearly the same as describe_card's (similarity 0.65); only the names and schemas tell them apart. Say in this description when to use describe_card instead.confusable_pair
Minor
Says nothing about what it returns.no_return_info

find_model

61 / 100Cloudy

Purpose: 17 / 20
When to use: 5 / 20
Arguments: 20 / 25
Return value: 7 / 15
Constraints and side effects: 7 / 10
Examples: 5 / 10

No issues.

verify_receipt

61 / 100Cloudy

Purpose: 17 / 20
When to use: 5 / 20
Arguments: 20 / 25
Return value: 7 / 15
Constraints and side effects: 7 / 10
Examples: 5 / 10

Minor
The description mentions none of its 3 or more arguments.params_not_in_description

find_flip

62 / 100Cloudy

Purpose: 17 / 20
When to use: 5 / 20
Arguments: 16 / 25
Return value: 7 / 15
Constraints and side effects: 7 / 10
Examples: 10 / 10

Minor
Arguments without a description: level.quantity, level.value.param_no_description
Minor
String arguments with no constraint or example: level.quantity.loose_string_param

run_trajectory

63 / 100Cloudy

Purpose: 17 / 20
When to use: 5 / 20
Arguments: 14 / 25
Return value: 7 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

Major
Arguments without a description: segments[].steps, segments[].signed.alg, segments[].signed.key, segments[].signed.instrument, segments[].signed.time, segments[].signed.seq, segments[].signed.prev, segments[].signed.challenge, segments[].signed.sig, readout.first_past.quantity, readout.first_past.above, readout.first_past.below, from.request, from.run_seal, from.coupling.param_no_description
Minor
String arguments with no constraint or example: segments[].signed.time, readout.first_past.quantity, from.coupling.loose_string_param

verify_dataset

63 / 100Cloudy

Purpose: 17 / 20
When to use: 10 / 20
Arguments: 19 / 25
Return value: 0 / 15
Constraints and side effects: 7 / 10
Examples: 10 / 10

Minor
No `required` list, so every argument is optional.no_required
Minor
Says nothing about what it returns.no_return_info

What static scoring cannot tell

This score reads only the text of each description and schema: it says what is written, not what a model will do. Short tools whose names already say what they do, such as browser_close, score low here even when models use them well, and in our measurements current models chose the right tool in one step even from one-line descriptions, as long as the names and schemas differed. What the text cannot show, such as what happens over several steps and whether an added sentence helps or misleads, is what an evaluation measures, on the Pro and Team plans.

Is your server listed here and you would rather it were not? Email support@forecall.dev, and we will take it off within 7 days.

All scored servers