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.

Create Agent Wallet

create_agent_wallet

Convenience tool: generate a new XRPL keypair and return the seed.

⚠ NOT RECOMMENDED FOR PRODUCTION. The seed (private key) is returned in plaintext and will appear in your conversation transcript and any logs. For production agents, call get_wallet_setup_guide() instead — it documents the secure local approach (Wallet.generate() + seed in .env) where the seed never leaves your environment.

Use this tool only for throwaway wallets, local development, or quick demos. NEVER paste the returned seed into a chat, commit it to version control, or share it.

The wallet is NOT yet active on the ledger — fund it before use. XRPL requires 1 XRP minimum to activate a wallet (base reserve). Until funded:

  • You cannot sign or submit transactions

  • You cannot be the destination of an EscrowCreate (buyer's tx will fail)

  • Your trust score will show as 0 / "not found"

Funding options:

  • Call fund_xrpl_wallet_via_coinbase(address, usd_amount=5.0) if you have USDC on Coinbase

  • Ask your operator or client to send ≥ 1 XRP to the address

  • Buy XRP on any exchange (Coinbase, Kraken, Binance) and withdraw to the address

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_agent_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say this is a non-read-only, non-idempotent, non-destructive call; the description adds the critical traits the annotations cannot: the private seed is returned in plaintext and lands in transcript/logs, and the wallet is inactive until funded. It spells out concrete consequences of an unfunded wallet (cannot sign, cannot receive EscrowCreate, trust score 0), which is exactly the behavioral context an agent needs before calling.

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 purpose then the production warning, and the funding consequences are cleanly bulleted. Slightly redundant: the plaintext-seed risk is restated in the 'NEVER paste the returned seed' line, which repeats the earlier warning rather than adding a new constraint.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-arg tool with an output schema, the description covers what the annotations and schema cannot: security posture, wallet lifecycle state, activation requirements, and next-step funding paths. An agent can call it and correctly handle the result without further documentation.

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?

The tool takes zero parameters, so the baseline is 4 and the description correctly adds no parameter noise. The useful semantic content it does supply — the address returned needs ≥1 XRP to activate — is contextual rather than parametric.

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 — 'generate a new XRPL keypair and return the seed' — and immediately frames it as a convenience tool, which separates it from get_wallet_setup_guide (secure approach) and create_testnet_wallet. An agent can tell exactly what it produces 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 Guidelines5/5

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

Gives explicit when-to-use ('only for throwaway wallets, local development, or quick demos') and when-not ('NOT RECOMMENDED FOR PRODUCTION'), and names the concrete alternative (get_wallet_setup_guide) plus the funding follow-up (fund_xrpl_wallet_via_coinbase). Nothing 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.

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