Skip to main content
Glama

ProofTask public

getResultStatus

Read-onlyIdempotent

[No connection needed] Read signed public status using an existing disclosed status-link resultId (result_ + 64 hex), not a Conformity Record URN. Discloses status only, never content. 404 means unknown, withdrawn from disclosure or retired. Verify offline with independently confirmed issuer keys; see /developers/mcp.md.

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": {
      "resultId": "<resultId>"
    },
    "name": "getResultStatus"
  }
}

Input Schema

NameRequiredDescriptionDefault
resultIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, it discloses that no live connection is needed, that only status is revealed and never content, and that 404 collapses three distinct cases (unknown, withdrawn, retired). It also states the trust model: verify offline with independently confirmed issuer keys. This is substantive behavior an agent could not infer from the annotations alone.

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

Conciseness4/5

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

Three dense sentences, front-loaded with the no-connection qualifier and the identifier requirement, with no filler. The compact phrasing is efficient but slightly telegraphic, costing a bit of readability.

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?

For a single-parameter read with no output schema, the definition covers input origin, scope of disclosure, and the 404 case, plus a documentation pointer. It does not describe the returned status values or their meaning, which is the main remaining gap.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must carry meaning for the single parameter, and it does: it explains the identifier's origin (a disclosed status-link), its visual format (result_ + 64 hex), and what it is not (a Conformity Record URN). It stops short of explaining whether the ID is case-sensitive or how it is obtained, leaving a small gap.

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

Purpose5/5

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

The description states a specific verb and resource ('Read signed public status') and pins down the exact identifier type required ('existing disclosed status-link resultId (result_ + 64 hex)'), explicitly excluding a Conformity Record URN. An agent can tell what this retrieves without opening the schema.

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

Usage Guidelines4/5

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

It gives a clear selection condition: use this only with an already-disclosed status-link resultId, not a Conformity Record URN, and it routes the caller to /developers/mcp.md for verification details. It does not name a sibling tool as an alternative, so it falls short of full when/when-not routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources