Skip to main content
Glama

Bureau Threshold Check

bureau_verify_threshold
Read-onlyIdempotent

Boolean creditworthiness check: is this XRPL wallet's Agent Credit Bureau score above the required threshold? Returns a yes/no answer without exposing the full report. Cost: 0.005 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_verify_threshold"
  }
}

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.2/5.0
Behavior3/5

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

Adds two things annotations cannot convey: a concrete price of 0.005 RLUSD and the settlement dependency on the payment_token argument, plus the privacy behavior of not exposing the full report. It does not say what happens if settlement is missing or invalid, whether results are cached, or where the threshold value comes from, so the mutation-adjacent payment flow stays underspecified.

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?

Three short sentences, front-loaded with the question being answered, then the privacy guarantee, then the cost. Nothing redundant and no filler.

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, non-destructive read tool with full schema coverage and no output schema, this covers purpose, output shape, cost, and side-effect profile adequately. The remaining gap is operational: the threshold's origin and the failure behavior when payment_token is absent are unstated.

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 coverage is already 100%, and the description still adds value by quantifying the cost that payment_token must settle (0.005 RLUSD) and tying that argument to the price, which the schema only describes abstractly as 'proving settlement'. The wallet parameter gets no added meaning beyond the schema's address format note.

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 — a boolean check of an XRPL wallet's Agent Credit Bureau score against a required threshold — and immediately scopes the output as yes/no rather than a full report, which distinguishes it from the sibling bureau_full_report. The caller knows exactly what question the tool answers.

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?

Explicitly frames the context: use this when a yes/no answer suffices and the full report should not be exposed. It never names a sibling tool, so the routing to bureau_full_report or bureau_public_score is left to inference, but the selection criterion (boolean vs. full report) is clear.

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