Skip to main content
Glama
Sign In
AgentWorld MCP Server

AgentWorld MCP Server

by shawnhvac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

exec_escrow_info

Explains how tool-execution escrow releases payment only against a signed provider I/O log, halts and refunds on tampered proofs, and returns routes, failure codes, and demo details.

Instructions

Describe the Verifiable Tool-Execution Escrow at x402-agent-pay.com — escrow that releases payment only against a provider signature over the tool's actual I/O log. Tampered proofs halt the escrow and refund the buyer. Returns the live routes, verification failure codes, and a paid demo ($0.05 USDC via x402 on Base).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does meaningful work: it discloses the escrow release condition, the tamper consequence (halt and refund), and enumerates what the response contains (live routes, verification failure codes, a paid demo). The main gap is that it does not say whether calling this tool itself is free or incurs the x402 charge, which is the single most decision-relevant fact for an agent with a budget.

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?

Three sentences, front-loaded with the resource and mechanism, then payoff behavior, then payload contents. Dense but each sentence adds information; the appended '$0.05 USDC via x402 on Base' is useful rather than filler. Minor cost: it reads slightly like marketing copy for the product rather than a tool spec.

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?

For a zero-parameter informational tool with no output schema, the description covers what the resource is, how it behaves, and roughly what comes back, which is close to sufficient. It falls short of a 5 because it omits whether invocation is free versus paid and gives no routing signal versus the many sibling *_info endpoints.

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 with a closed schema, so there is no parameter meaning to add; baseline is 4. The description correctly does not waste space describing inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: describing the Verifiable Tool-Execution Escrow at x402-agent-pay.com, and explains the escrow's core mechanism (payment released only against a provider signature over the tool's I/O log). It is clearly distinguishable in kind from sibling info tools, though it never names or contrasts against near-neighbors such as earn_escrow_info, settlement_rail_info, or pay_to_call_info.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the documentation/discovery endpoint for the escrow product, and the mention of a $0.05 USDC demo hints at an evaluation path. There is no explicit 'use this when…' guidance, no exclusions, and no pointer to which sibling covers related settlement or payment topics.

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

Deploy Server

Other Tools