Skip to main content
Glama

Verify Bureau Attestation

bureau_verify_attestation
Read-onlyIdempotent

Verify an Agent Credit Bureau attestation JWT issued by bureau_get_attestation: confirms the signature, the wallet, its 300-850 score and grade, loyalty and KYB tiers, and that the token has not expired. Read-only. Free.

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": {
      "token": "<token>"
    },
    "name": "bureau_verify_attestation"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesAttestation JWT issued by bureau_get_attestation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / token / description
      Added value: +"Attestation JWT issued by bureau_get_attestation"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, yet the description still adds real value: the list of what is actually validated, the expiry check, and the cost model ('Free'). 'Read-only' merely restates the annotation, and it does not say what happens on an invalid or tampered token.

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?

A single dense sentence with the action front-loaded, followed by two short status fragments. Every enumerated check is informative, though 'Read-only' duplicates the annotation and could be dropped without loss.

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

Completeness3/5

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

For a one-parameter, annotation-rich tool the invocation side is fully covered, but no output schema exists and the description never indicates what verification returns (a validity flag, decoded claims, failure reasons). That return-shape gap keeps it at minimum-viable rather than complete.

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?

Only one parameter with 100% schema description coverage, so the schema already carries the meaning. The description reinforces the token's provenance but adds no format, encoding, or expiry-handling detail beyond what the schema states, matching the high-coverage baseline of 3.

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?

Specific verb ('Verify') plus a precisely named resource ('Agent Credit Bureau attestation JWT') tied to its issuing sibling, bureau_get_attestation. The enumerated checks (signature, wallet, score/grade, loyalty and KYB tiers, expiry) make it unmistakable versus bureau_verify_threshold or verify_payment.

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 states the precondition clearly: the token must come from bureau_get_attestation, which implies the verify-after-issue workflow. It stops short of an explicit exclusion against the closely named sibling bureau_verify_threshold, so the when-not condition is left to inference.

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