LLPRO Campus

Verify a stamp

countersign_verify

Read-onlyIdempotent

Confirm a Countersign stamp is real: give a stamp id (and optionally the work, to confirm the stamp is for exactly that text). Returns whether it is in the public log and whether its hash and signature are valid.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "countersign_verify"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`output`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A3.8/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover read-only, idempotent, non-destructive and closed-world behavior, so the bar is lower, and the description adds real context beyond them: it discloses that verification checks public-log inclusion plus hash and signature validity. That is exactly the behavioral detail an agent needs to trust the result. It does not say what a negative result looks like, keeping it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences: the action and its inputs first, the return values second. The parenthetical only clarifies the optional parameter's purpose, so nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly shoulders the return-value explanation by naming the three verification outcomes. For a two-parameter read tool this is nearly complete, with only the id format and the 'output' vs 'the work' naming mismatch left open.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry the parameter burden. It explains the required id and an optional second input ('the work … exactly that text'), but the schema calls that second property 'output', so the mapping between 'the work' and 'output' is left ambiguous, and no id format is given.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource: 'Confirm a Countersign stamp is real', and states exactly what it returns (public-log membership, hash validity, signature validity). It is clearly not the stamping tool or the log tool, though it never names a sibling to sharpen the distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied through the input requirements ('give a stamp id', optionally 'the work'), but there is no explicit when-to-use/when-not-to-use guidance and no alternative tool is named for the case where you want to create or list stamps.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All LLPRO Campus tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?