Atomadic MCP

Escrow Create

escrow_create

[defi] Create agent-to-agent escrow

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": {
      "payer_id": "<payer_id>",
      "payee_id": "<payee_id>",
      "amount": "<amount>",
      "currency": "<currency>"
    },
    "name": "escrow_create"
  }
}

Input Schema

Name	Required	Description	Default
`amount`	Yes
`currency`	Yes
`payee_id`	Yes
`payer_id`	Yes
`conditions`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 17, 2026

TDQS

C2/5.0

Behavior2/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false, openWorld=false, so mutation and non-idempotency are known. The description adds nothing beyond that: no mention of funds being locked, what happens on duplicate calls (non-idempotent means real financial risk), or permission/balance requirements for a money-moving operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded, but the brevity is under-specification rather than economy; a single six-word phrase cannot carry the semantics of a financial escrow creation tool.

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

Completeness1/5

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

For a non-idempotent, money-moving tool with a nested conditions object, 0% schema coverage and no output schema, the description leaves essentially everything unspecified: fund custody, condition schema, release path, and return value.

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

Parameters1/5

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

Schema description coverage is 0% across five parameters, including a nested "conditions" object whose shape and semantics are entirely undocumented. The description says nothing about amount/currency format, payer/payee identifier expectations, or what conditions gate release, so it provides zero compensation for the coverage gap.

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

Purpose3/5

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

States a verb and resource ("Create ... escrow") with a modifier ("agent-to-agent"), so the core action is identifiable. But it never says what an escrow here entails (funds held pending release? condition-gated?) and gives no explicit differentiation from sibling escrow_release/escrow_dispute beyond the verb.

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

Usage Guidelines2/5

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

No when-to-use, prerequisites, or alternatives are given. The agent must infer from the name alone that this is the first step before escrow_release or escrow_dispute, and nothing indicates what must exist (e.g., registered agents) before calling it.

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

All Atomadic MCP 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.

Resources

Need Help?