Live-payload conformance probes with signed receipts: ABSENT/EMPTY/PARTIAL/COMPLETE/BROKEN.
Scored across 1 tool
Only one tool exists, so there is no possibility of selecting the wrong tool. The single purpose is clearly stated.
With a single tool, naming is trivially consistent. The name 'conformance_check' follows a clear snake_case convention.
A single tool is borderline thin for an MCP server, even if it matches a narrow purpose. The server could benefit from supporting operations like schema registration or receipt verification.
The core check operation is present, but the domain lifecycle likely includes registering schemas, listing checks, and verifying receipts. These missing operations create notable gaps.
Run one live-payload conformance check against a registered declared schema; returns a signed receipt. $0.01/check via x402.
| Name | Required | Description | Default |
|---|---|---|---|
| tool | Yes | ||
| server_id | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden, and it does disclose two meaningful traits: the per-call cost and payment channel (x402) and the return shape (signed receipt). It does not disclose the side-effect risk of submitting a 'live payload' to a target server, nor error/retry behavior, which is a real gap for a tool that touches external systems.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short, front-loaded sentences with zero filler; the core action comes first, the return value and cost follow. Nothing is repeated that the schema or annotations already provide.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a two-required-parameter tool with no annotations, no output schema and 0% schema coverage, the description is too thin: it never explains the parameters, the registration precondition, or the side effects of sending a live payload. The cost and receipt notes are helpful but far from complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% and the description never mentions either parameter. It only hints that a 'registered declared schema' and a 'live payload' are involved, leaving 'server_id' and 'tool' — including the fact that 'tool' identifies the schema/tool under test — undocumented in both places.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (run a conformance check) on a specific resource (a live payload validated against a registered declared schema) and notes the returned artifact (a signed receipt). The live-payload-vs-declared-schema distinction is informative, though the phrasing is jargon-dense and no siblings exist to differentiate against.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no statement of when to use this tool, when not to, what prerequisites exist (e.g., must the server be registered first?), or what happens on failure. The only implied context is the cost line, which implies payment but not usage conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
conformance_checkCheck what a paid x402 endpoint or MCP server delivered, from probes anyone can repeat.
Dependency-probe-gated exit execution with hash-verified extraction and signed receipts.
The evidence layer for MCP: live operational grades plus Trust Receipts for every registry server.
Contradiction-verified, freshness-SLA'd signed feed: per-record status + as-of date + receipt.
Add one secure layer between your agents and this server.