Skip to main content
Glama

Bureau Public Score

bureau_public_score
Read-onlyIdempotent

FICO-style Agent Credit Bureau score for any XRPL wallet on the public 300-850 scale: returns the score, letter grade, loyalty tier, blocked status, and generation timestamp, computed from the wallet's recorded payment history. Wallets with no credit history return 404; use bureau_full_report for the paid score breakdown. 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": {
      "wallet": "<wallet>"
    },
    "name": "bureau_public_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletYesXRPL classic address (r...) of the wallet to look up

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered; the description adds real context on top by disclosing the 404 outcome for wallets with no credit history, the cost model, and the fact that the score derives from recorded payment history. It stops short of describing latency, caching, or how scores are computed, which keeps it below the top mark.

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?

Four short sentences, front-loaded with the core purpose and scale before the return fields, sibling pointer, and cost/safety flags. Every sentence adds information an agent needs; nothing is redundant with the annotations or schema.

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?

There is no output schema, so the description correctly carries the return burden by listing score, letter grade, loyalty tier, blocked status, and timestamp, plus the 404 case and the paid alternative. It leaves loose ends such as what the loyalty tier values mean and whether 'blocked' affects usability, but the definition is sufficient to invoke the tool correctly.

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% and the single wallet parameter is fully documented as an XRPL classic address, so the schema does the heavy lifting. The description adds only the mild implication that any XRPL wallet qualifies and that history-less wallets produce a 404 — a behavioral note rather than parameter semantics, so the 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-and-resource combination (compute/return a FICO-style bureau score for an XRPL wallet), names the output scale (300-850), enumerates the returned fields, and explicitly distinguishes itself from bureau_full_report. An agent can tell this apart from the paid-report sibling 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 Guidelines5/5

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

Gives an explicit routing rule: use this tool for the free public score, use bureau_full_report when the paid score breakdown is needed. It also flags the cost difference ('Free') and the read-only nature, so the agent knows both when to pick it and when to defer to the alternative.

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