Skip to main content
Glama

Issue Bureau Attestation

bureau_get_attestation

Issue a portable Agent Credit Bureau attestation JWT (24-hour TTL) proving an XRPL wallet's creditworthiness; any third party can verify it with bureau_verify_attestation. Cost: 0.01 RLUSD, paid via the payment_token argument.

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": {
      "wallet": "<wallet>"
    },
    "name": "bureau_get_attestation"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletYesXRPL classic address (r...) of the wallet to look up
payment_tokenNoPayment token proving settlement of this tool's RLUSD price

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / payment_token / description
      Added value: +"Payment token proving settlement of this tool's RLUSD price"
    • addedInput schema / properties / wallet / description
      Added value: +"XRPL classic address (r...) of the wallet to look up"
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare the coarse safety profile (write, non-idempotent, non-destructive, closed-world); the description adds the traits that actually change agent behavior: the artifact produced is a JWT, it expires after 24 hours, it is third-party verifiable, and each call carries a 0.01 RLUSD charge settled through payment_token. Cost and TTL are nowhere in the structured fields and are exactly what an agent needs before calling a paid, non-idempotent tool.

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?

A single dense sentence that front-loads the action and artifact, then appends verification path and cost. No filler, no restatement of the title, and every clause carries information an agent needs.

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 carries the return-value burden and does so by naming the artifact, its TTL, and its verifiability. It leaves open what the JWT asserts about creditworthiness, what happens if the wallet has little history, and what failure looks like when payment_token is missing or invalid — minor but real gaps for a paid issuance tool.

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 100%, so both parameters are already documented, and the schema's own text for payment_token nearly duplicates the description. The description does contribute the concrete price (0.01 RLUSD) attached to payment_token, but adds nothing about wallet format or lookup behavior beyond the schema's 'XRPL classic address (r...)' note. Baseline 3 is appropriate.

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?

States a specific verb ('Issue') plus a precisely scoped resource ('portable Agent Credit Bureau attestation JWT') and its meaning ('proving an XRPL wallet's creditworthiness'). It also names the sibling that consumes the output (bureau_verify_attestation), so an agent can tell issuance from verification without opening either 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?

Gives clear context for use — obtain a wallet's credit attestation — and routes the counterpart action to bureau_verify_attestation. It also states the prerequisite cost of 0.01 RLUSD via payment_token, which is actionable guidance. It stops short of saying when to prefer bureau_full_report or bureau_public_score instead, so it lacks explicit exclusions.

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