MM by Escrow MCP

Accept delivery and release payment (buyer)

mm_accept_delivery

Destructive

Releases the delivered milestone (or the whole deal) to the seller. This cannot be undone.

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": {
      "deal_id": "<deal_id>",
      "token": "<token>"
    },
    "name": "mm_accept_delivery"
  }
}

Input Schema

Name	Required	Description
`token`	Yes	Your private deal token (from mm_create_deal or your deal link ?k=...)
`deal_id`	Yes	Deal ID, like D-7KQ2M9AB
`milestone_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The annotation already flags destructiveHint=true, and the description adds the substantive consequence: funds are released to the seller and the action cannot be undone. It does not mention preconditions (the milestone must already be marked delivered) or that a valid deal token is required, which leaves some behavioral gaps.

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?

Two short sentences, front-loaded with the action and immediately followed by the irreversibility warning. No filler or redundant restatement of the title.

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 destructive, no-output-schema mutation tool, the description covers what happens and the irreversibility, which is the core an agent needs. It stops short of stating prerequisites (delivery must be confirmed first) or the auth requirement behind the token parameter.

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 coverage is 67%, with milestone_id carrying no schema description. The parenthetical '(or the whole deal)' implicitly explains that omitting milestone_id accepts the entire deal, which is genuinely useful, but deal_id and token semantics are left entirely to the schema.

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 effect ('releases the delivered milestone ... to the seller') and scopes it to two cases: a single milestone or the whole deal. The title adds the buyer-side role, which separates it from seller-side siblings like mm_mark_delivered, though no sibling is named in the description itself.

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 implied by 'delivered milestone' — the agent can infer this applies after delivery is marked. There is no explicit when-not guidance and no pointer to alternatives such as mm_open_dispute or mm_refund_buyer, which matter given the irreversible nature of the call.

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

All MM by Escrow 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?