Skip to main content
Glama
Sign In

AgentTrust XRPL

by io.github.eamwhite1
OverviewDiscussionsAdmin

Try Testnet Demo

try_testnet_demo

Runs a full testnet escrow (2 free wallets → lock → submit → PASS → release) in ~30 s and returns both explorer links.

Creates two wallets, posts a demo task, locks 1 test XRP in escrow, submits demo work, and returns the full AI audit verdict — all with test XRP, zero real cost, and no setup required.

Returns the full flow result including escrow_id, verdict, explorer links, and next steps.

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": "try_testnet_demo"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare non-read-only, open-world, non-idempotent, and non-destructive behavior. The description adds meaningful context beyond that: it creates two wallets, locks 1 test XRP, submits demo work, returns an AI audit verdict, takes about 30 seconds, and returns explorer links; it does not cover permissions or rate limits.

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?

The first sentence front-loads the key action, duration, and return value. The following sentences elaborate usefully, though they partially repeat the wallet-creation and return-link details, adding some redundancy.

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?

The output schema covers return values and annotations cover safety traits, so the description need not restate them. It sufficiently explains the flow, cost, timing, and outputs, though it could state more explicitly whether repeated calls create persistent testnet artifacts.

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 there are no parameter semantics to explain. Per the rubric, a zero-parameter tool receives a baseline of 4.

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: 'Runs a full testnet escrow' and enumerates the full flow (wallets → lock → submit → PASS → release). It clearly distinguishes itself from granular siblings by being an all-in-one demo flow.

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?

Makes the usage context clear: a testnet demo that costs zero real XRP and requires no setup, useful for trying the flow quickly. It does not explicitly name alternatives or when-not-to-use cases, so it falls short of the top score.

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