Skip to main content
Glama
Sign In

AgentTrust

by io.github.eamwhite1
OverviewDiscussionsAdmin
This connector has been deprecated

This connector has been replaced by xrpl-referee.

Register Wallet Free Tier

register_wallet_free_tier

Register an existing wallet for 3 free escrows by proving ownership.

Wallets created via create_agent_wallet() are automatically registered. If you created your wallet elsewhere (Wallet.create(), Privy, Xaman, etc.), call this to claim the same 3 free escrows.

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>",
      "tx_hash": "<tx_hash>"
    },
    "name": "register_wallet_free_tier"
  }
}

Input Schema

NameRequiredDescriptionDefault
tx_hashYesHash of an XRPL AccountSet tx you submitted from wallet_address with a Memo containing the challenge string from get_wallet_verification_challenge(). This proves you own the wallet.
wallet_addressYesYour XRPL wallet address (r...) to register for the free tier.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, open-world, non-idempotent, non-destructive operation. The description adds the meaningful prerequisite that ownership must be proven via a challenge/verification flow, but it does not explain what happens on re-registration (relevant given idempotentHint=false) or on a failed/expired challenge.

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 action and the eligibility condition; the create_agent_wallet exclusion comes second and every sentence earns its place.

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?

An output schema exists, so return values need not be described, and the description covers the trigger condition and the verification prerequisite. It stops short of covering failure/re-registration behavior, which is the only notable 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 description coverage is 100%: tx_hash and wallet_address are fully documented in the schema, including the XRPL AccountSet memo-challenge requirement. The description adds only the framing of 'proving ownership', 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 (register) and resource (an existing wallet for the free tier) plus the means (proving ownership). It also explicitly distinguishes itself from create_agent_wallet(), which auto-registers, so an agent can tell the two apart 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 when-to-use ('If you created your wallet elsewhere (Wallet.create(), Privy, Xaman, etc.)') and a when-not-to-use ('Wallets created via create_agent_wallet() are automatically registered'), naming the alternative tool directly.

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

All AgentTrust 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