Skip to main content
Glama
Sign In

AgentTrust XRPL

by io.github.eamwhite1
OverviewDiscussionsAdmin

Check Wallet KYC Status

check_wallet_kyc
Read-onlyIdempotent

Check identity verification status for a wallet operator.

Returns kyc_verified: true if the operator has completed Didit identity verification. Verified wallets unlock escrows up to $10,000 (vs. the default $3,000 cap).

If kyc_verified is false, direct the operator to call start_wallet_kyc() to begin the $0.50 identity verification flow.

Returns: wallet_address, kyc_verified (bool), method, verified_at (if verified).

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_address": "<wallet_address>"
    },
    "name": "check_wallet_kyc"
  }
}

Input Schema

NameRequiredDescriptionDefault
wallet_addressYesThe XRPL wallet address (r...) to check KYC status for.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / wallet_address / title
      Added value: +"XRPL Wallet Address"
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, open-world profile, and the description adds genuine domain context beyond them: the verification provider (Didit), the escrow-cap consequence of the result, and the cost of the remediation step. It omits failure modes such as an invalid or unregistered wallet address, and the explicit 'Returns:' list largely duplicates the output schema.

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-loads the purpose, then the meaning of the result and the remediation path; each sentence carries information except the trailing 'Returns:' line, which restates the output schema and could be dropped.

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 single-param read tool with full annotations and an output schema, the definition covers what it does, what the result means, and the next step. The remaining gap is edge-case behavior (unknown wallet, pending verification, provider outage), which an agent might reasonably want before calling.

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 schema description coverage is 100%, so the schema already documents the XRPL address format ('r...'). The description adds only a mild nuance by framing the address as belonging to a wallet operator; it provides no extra syntax, validation, or format detail.

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 (check) and resource (wallet operator identity verification status), and the follow-up paragraph implicitly separates it from start_wallet_kyc, which initiates the flow rather than reading state. An agent can distinguish read-status from the sibling that starts verification without opening the 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 concrete routing rule: when kyc_verified is false, direct the operator to start_wallet_kyc() for the $0.50 flow, and explains why it matters (escrow cap of $3,000 vs $10,000). It does not explicitly state prerequisites (e.g., whether to call before prepare_escrow or fund flows), so it stops short of full when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AgentTrust XRPL toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources