Skip to main content
Glama

Get Agent Passport

get_agent_passport
Read-onlyIdempotent

Full Agent Passport for any XRPL wallet: registered domain, first/last seen timestamps, total calls and total spend, risk score 0-100, KYB tier, loyalty tier, free-credit balance, and blocked status from the wallet's recorded 402Proof payment history. Returns 404 for wallets with no recorded history. 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": "get_agent_passport"
  }
}

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

A3.9/5.0
Behavior3/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 useful context beyond that: the data source (recorded 402Proof payment history), the 404-on-no-history behavior, and that the call is free. It does not describe response shape or latency, but with annotations carrying the safety burden a 3 is fair.

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?

Front-loaded with the resource and its full field list, followed by two short sentences covering the 404 case and the read-only/free traits. Dense but every clause carries information; the field enumeration is long but earns its place given there is no output 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?

With no output schema, the description compensates by enumerating the returned fields and the risk-score range (0-100), plus the 404 edge case. Complete enough for a single-parameter read tool; only the response envelope/format is left unspecified.

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, and the schema already documents it at 100% coverage as an XRPL classic address (r...). The description's "any XRPL wallet" adds no format or constraint detail beyond the schema, so the baseline 3 applies.

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 ("Full Agent Passport for any XRPL wallet") and enumerates the exact contents returned: domain, timestamps, call/spend totals, risk score, KYB tier, loyalty tier, credit balance, blocked status. An agent can distinguish this from siblings like bureau_full_report or bureau_public_score without opening a 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 a clear usage context (look up any XRPL wallet's passport) and a concrete boundary condition: 404 for wallets with no recorded history. It does not explicitly name when to prefer a sibling such as bureau_full_report or bureau_public_score, so routing between the bureau tools 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