MM by Escrow MCP

Set up bank payouts (card / bank deals, seller)

mm_get_payout_setup_link

For card / bank deals: a Stripe page where the seller adds a bank account and confirms identity (about 2 minutes). The buyer can pay once this is done.

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_get_payout_setup_link"
  }
}

Input Schema

Name	Required	Description
`email`	No
`token`	Yes	Your private deal token (from mm_create_deal or your deal link ?k=...)
`country`	No	Two-letter country of the bank account, default US
`deal_id`	Yes	Deal ID, like D-7KQ2M9AB

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does add real context: the page is Stripe-hosted, seller-facing, takes about 2 minutes, and gates buyer payment. Missing are link lifetime, reusability/idempotency, and who is permitted to request it — all material for a link-generating tool.

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?

Two tight sentences, with the deal-type scope front-loaded ahead of the explanatory clause. 'About 2 minutes' earns its place by setting expectations for the seller handoff. Little waste overall.

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

Completeness3/5

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

For a four-parameter link tool with no annotations and no output schema, the description should say that a URL is returned for the agent to pass to the seller, and whether the link expires or can be regenerated. It covers the what and why well but leaves the delivery and lifecycle mechanics underspecified.

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 75%, so most parameters (token, deal_id, country) are already documented in the schema. The description adds no parameter-level meaning — notably it does not explain what 'email' is used for, though the seller-identity framing hints it may prefill Stripe onboarding. Baseline 3 applies.

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?

The description states a concrete resource and audience: a Stripe-hosted page where the seller adds a bank account and confirms identity, scoped to card/bank deals. It does not literally say the tool returns a link/URL, which is left to the name, but the purpose is otherwise unambiguous and distinguishable from buyer-side siblings like mm_get_payment_link.

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?

Scope is given ('For card / bank deals') and an implicit precondition is stated ('the buyer can pay once this is done'), which implies when to call it. However, no alternative is named (e.g., for non-card/bank deal payment flows) and there is no guidance on what to do if the seller has already completed setup.

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?