Skip to main content
Glama

Bureau Full Report

bureau_full_report
Read-onlyIdempotent

Full Agent Credit Bureau report for an XRPL wallet: 300-850 score breakdown, spend history, and risk factors. Cost: 0.01 RLUSD, paid via the payment_token argument. Read-only.

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_full_report"
  }
}

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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral information that annotations and schema do not carry: a fixed price of 0.01 RLUSD and the requirement to settle it through payment_token. It stops short of saying what happens if payment is missing or insufficient.

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 tightly packed sentences: payload first, then cost mechanism and read-only status. No filler, no redundancy, and the most decision-relevant content (what you get, what it costs) is front-loaded.

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 two-parameter read tool with no output schema, the description covers what comes back at a summary level and the payment precondition, which is the main thing an agent could trip over. Only edge-case behavior (unpaid/invalid token, response shape details) is left unaddressed, which is a modest gap.

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 fully documented, including that payment_token proves settlement. The description's only added semantic value is the concrete price (0.01 RLUSD) tied to that token; it adds nothing about wallet formatting beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 resource ('Full Agent Credit Bureau report') and scopes it to an XRPL wallet, then enumerates the payload (score breakdown, spend history, risk factors). The word 'Full' implicitly signals a difference from the sibling bureau_public_score, but no sibling is named explicitly, so differentiation relies on inference.

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 rather than stated: an agent can infer this is the comprehensive variant versus the 'public score' sibling from the word 'Full', but there is no explicit when-to-use / when-not-to-use guidance or named alternative. A reader must connect the dots themselves.

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