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.

Submit Escrow Transaction

submit_escrow_transaction
Destructive

Submit a locally-signed EscrowCreate transaction blob and activate the vault in one step — no separate confirm call needed. Free to try: pass network='testnet' (see create_testnet_wallet / try_testnet_demo).

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": {
      "escrow_id": "<escrow_id>",
      "tx_blob": "<tx_blob>"
    },
    "name": "submit_escrow_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
tx_blobYesHex-encoded signed transaction from your XRPL wallet
escrow_idYesThe escrow ID from hire_and_pay() or create_escrow_vault()

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is covered. The description adds useful behavioral context: the blob is locally signed, the call activates the vault, and it combines submission with activation so no separate confirm call is needed.

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 description is short and front-loads the main action and one-step behavior. The testnet sentence is useful in intent but introduces a misleading parameter instruction, slightly reducing structure quality.

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

Completeness3/5

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

The presence of an output schema and rich annotations reduces what the description must explain, and it does explain the one-step submission/activation flow. However, the nonexistent network parameter instruction creates a real gap for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents escrow_id and tx_blob. But the description adds incorrect parameter guidance by telling users to pass network='testnet', while the schema has additionalProperties=false and no network field, which could cause invalid calls.

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?

The description gives a specific verb and resource: submit a locally-signed EscrowCreate transaction blob and activate the vault. It also distinguishes the operation from a separate confirm step, making it clear how it differs from confirm_escrow_transaction.

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?

It explicitly says no separate confirm call is needed, which helps the agent choose this tool over the confirm path, and it points testnet users toward create_testnet_wallet / try_testnet_demo. However, the guidance to pass network='testnet' is misleading because network is not an accepted parameter in the schema.

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