AgentTrust XRPL

by io.github.eamwhite1

Overview Discussions Admin

Challenge Escrow Verdict

challenge_escrow_verdict

Submit a challenge against a PASS verdict during the challenge window.

Two-step process:

Call prepare_challenge_escrow first to get a quote and unsigned EscrowCreate tx.
Sign and submit the EscrowCreate (fee goes to worker address as escrow).
Call this tool with the resulting tx hash.

Outcomes:

PASS_UPHELD (challenge rejected): escrow releases to worker, fee released to worker.
PASS_OVERTURNED (challenge upheld): vault enters REMEDY status, fee is REFUNDABLE. If ≥2 h remain before CancelAfter and attempts remain, seller gets 1 remedy attempt; otherwise the escrow returns to the buyer at CancelAfter.
REVIEW_INCONCLUSIVE (Pro unavailable): escrow releases to worker, fee is REFUNDABLE.

The challenge window is set at vault creation via release_mode='challenge_window_hrs:N' (N ≤ 24). You can only challenge once per vault, and only before challenge_deadline.

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>",
      "quote_id": "<quote_id>",
      "fee_tx_hash": "<fee_tx_hash>",
      "challenger_address": "<challenger_address>"
    },
    "name": "challenge_escrow_verdict"
  }
}

Input Schema

Name	Required	Description
`reason`	No	Optional: explain specifically why the work does not satisfy the listed criteria.
`quote_id`	Yes	The quote ID from prepare_challenge_escrow. Contains the fee amount and condition.
`escrow_id`	Yes	The receipt code for the escrow whose PASS verdict you want to dispute.
`fee_tx_hash`	Yes	64-char XRPL tx hash of the EscrowCreate you signed and submitted (from the unsigned_tx in the quote).
`criteria_ids`	No	Optional: one or more criterion IDs you believe the work failed. If omitted, the full verdict is reviewed.
`challenger_address`	Yes	Your XRPL wallet address (r...) — must match the buyer on this vault.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedOct 25, 2026

addedInput schema / properties / challenger_address

Added value: +{
+  "description": "Your XRPL wallet address (r...) — must match the buyer on this vault.",
+  "title": "Challenger XRPL Address",
+  "type": "string"
+}

changedInput schema / properties / criteria_ids / description

Previous value: -"One or more criterion IDs (from the vault's criteria list) that you believe the work failed. Get these from the evaluation_verdicts in the escrow response."New value: +"Optional: one or more criterion IDs you believe the work failed. If omitted, the full verdict is reviewed."

removedInput schema / properties / fee_tx_hash / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / fee_tx_hash / default
```
Removed value: -null
```

changedInput schema / properties / fee_tx_hash / description

Previous value: -"⚠️ Disputes coming soon — do not pay any fee. This parameter is reserved for future use."New value: +"64-char XRPL tx hash of the EscrowCreate you signed and submitted (from the unsigned_tx in the quote)."

changedInput schema / properties / fee_tx_hash / title

Previous value: -"Challenge Fee Payment Hash"New value: +"Challenge Fee EscrowCreate Hash"

addedInput schema / properties / fee_tx_hash / type
```
Added value: +"string"
```

addedInput schema / properties / quote_id

Added value: +{
+  "description": "The quote ID from prepare_challenge_escrow. Contains the fee amount and condition.",
+  "title": "Challenge Quote ID",
+  "type": "string"
+}

changedInput schema / properties / reason / description

Previous value: -"Explain specifically why the work does not satisfy the listed criteria. The Pro model will review this alongside the original work."New value: +"Optional: explain specifically why the work does not satisfy the listed criteria."

removedInput schema / properties / tx_hash

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Hash of an XRPL AccountSet tx submitted from wallet_address with a Memo containing the challenge string from get_wallet_verification_challenge(). Proves you own the buyer wallet.",
-  "title": "Ownership Verification Transaction Hash"
-}

removedInput schema / properties / wallet_address

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Your XRPL wallet address (r...) — must match the buyer on this vault.",
-  "title": "Buyer Wallet Address"
-}

changedInput schema / required

Previous value: -[
-  "escrow_id"
-]New value: +[
+  "escrow_id",
+  "quote_id",
+  "fee_tx_hash",
+  "challenger_address"
+]

Changed18 schema fields changedOct 24, 2026

addedInput schema / properties / criteria_ids / anyOf

Added value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / criteria_ids / default
```
Added value: +null
```
removedInput schema / properties / criteria_ids / items
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / criteria_ids / type
```
Removed value: -"array"
```

addedInput schema / properties / fee_tx_hash / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / fee_tx_hash / default
```
Added value: +null
```

changedInput schema / properties / fee_tx_hash / description

Previous value: -"64-char hex XRPL transaction hash paying CHALLENGE_FEE_XRP (default 0.5 XRP) to the protocol wallet. Refunded if your challenge is upheld; paid to the worker if rejected."New value: +"⚠️ Disputes coming soon — do not pay any fee. This parameter is reserved for future use."

removedInput schema / properties / fee_tx_hash / type
```
Removed value: -"string"
```

addedInput schema / properties / reason / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / reason / default
```
Added value: +null
```
removedInput schema / properties / reason / type
```
Removed value: -"string"
```

addedInput schema / properties / tx_hash / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / tx_hash / default
```
Added value: +null
```
removedInput schema / properties / tx_hash / type
```
Removed value: -"string"
```

addedInput schema / properties / wallet_address / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / wallet_address / default
```
Added value: +null
```
removedInput schema / properties / wallet_address / type
```
Removed value: -"string"
```

changedInput schema / required

Previous value: -[
-  "escrow_id",
-  "criteria_ids",
-  "reason",
-  "fee_tx_hash",
-  "wallet_address",
-  "tx_hash"
-]New value: +[
+  "escrow_id"
+]

AddedOct 23, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Adds substantial behavior beyond annotations by enumerating the three outcomes and explaining where the escrow and fee go in each case. It also discloses remedy-attempt conditions and CancelAfter behavior, which are critical for an irreversible challenge action.

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?

Front-loads the action and uses a short structured two-step process followed by outcome cases. Despite being longer than average, every section carries necessary operational or financial consequence information.

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?

The description covers prerequisites, transaction flow, constraints, and outcome semantics, while the annotations and output schema cover safety and return-shape details. It gives an agent everything needed to invoke this tool correctly.

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%, so the schema already documents each parameter in detail. The description reinforces the workflow source for quote_id and fee_tx_hash, but does not add much parameter syntax or meaning beyond the schema itself.

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: submit a challenge against a PASS verdict during the challenge window. It also distinguishes itself from the prerequisite sibling prepare_challenge_escrow and makes the disputed object explicit.

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?

Provides a clear three-step usage sequence: call prepare_challenge_escrow, sign/submit the EscrowCreate, then call this tool with the tx hash. It also states the key constraints: only once per vault, only before challenge_deadline, and the challenge window is configured at vault creation.

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

All AgentTrust XRPL tools Inspect

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.