AgentTrust

by eamwhite1

Overview Schema Source Related Servers Score Discussions Admin

Python

Remote

Hire and Pay

hire_and_pay

Hire a worker and lock payment in escrow with a single call that returns a ready-to-sign XRPL transaction.

Instructions

One-call shortcut to register an escrow vault AND get the ready-to-sign transaction.

This combines create_escrow_vault() + prepare_escrow() into a single call. The agent only needs to sign the returned transaction and confirm it — no manual XRPL transaction construction required.

Typical flow:

hire_and_pay() — register vault, get ready-to-sign EscrowCreate tx
Sign transaction with your wallet and submit to XRPL
confirm_escrow_transaction(escrow_id, tx_hash) — activate the vault
Worker submits work, agent calls evaluate_escrow_work() to release payment

Returns: escrow_id, transaction (ready-to-sign), condition, cancel_after_human, next_step instructions.

Input Schema

TableJSON Schema

Name	Required	Description
`task`	Yes	Detailed description of what the worker must deliver. The AI referee evaluates against this — be precise.
`fee_hash`	No	64-char hex hash of your $0.10 payment (XRP/RLUSD/USDC) to rmcSrkpZ2i2kuvtCPeTVetee9SixP4djR. Omit to use free tier (if eligible).
`escrow_id`	Yes	Unique receipt code for this escrow, e.g. AT-7X9K-2MQ4. Must be unique.
`amount_xrp`	Yes	Amount of XRP to lock in escrow as the bounty.
`buyer_name`	No	Your name or agent identifier.
`buyer_address`	Yes	Your XRPL wallet address (r...) — you are the buyer.
`worker_address`	Yes	XRPL address (r...) of the worker to hire directly. Get this from direct_hire() or award_job().
`cancel_after_hrs`	No	Hours until escrow auto-cancels if worker doesn't deliver. Default 168 = 7 days.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already provide readOnly=false and idempotent=false. The description adds meaningful context: the tool creates an escrow vault, returns a transaction the agent must sign, and the vault is only activated after a later confirmation step. It also clarifies that no manual XRPL transaction construction is required, which is useful behavioral information beyond the annotations.

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 front-loaded with the core purpose and uses a compact typical-flow list and return summary. Each section earns its place, though there is slight redundancy between the opening 'One-call shortcut' sentence and the following 'This combines...' sentence.

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?

Given the tool's complexity—combining vault creation and transaction preparation—the description is complete enough: it explains the workflow, required signing step, confirmation dependency, and next-step evaluation. An output schema exists, so the return list is a helpful supplement rather than a required replacement.

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 input schema already documents all 8 parameters thoroughly, including the fee_hash payment detail and default cancellation window. The description does not add much parameter-level meaning beyond referencing the returned escrow_id and transaction, which is consistent with the baseline score of 3.

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 states a specific verb and resource: it 'register[s] an escrow vault' and returns a 'ready-to-sign' EscrowCreate transaction. It explicitly distinguishes itself as a combined shortcut for create_escrow_vault() + prepare_escrow(), making its role clear against the sibling tools.

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?

The description gives clear usage context: use this when you want to hire and pay in one call and then sign/submit the returned transaction. It names the combined underlying functions and outlines the exact follow-up flow with confirm_escrow_transaction() and evaluate_escrow_work(), though it does not explicitly state when NOT to use the standalone alternatives.

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