MM by Escrow MCP

Buy USDC with a card (USDC deals)

mm_buy_usdc_link

For USDC deals on Base: a Coinbase page to buy the USDC needed with a card or Apple Pay, delivered to the given wallet. Then lock it with mm_get_funding_request.

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>",
      "wallet_address": "<wallet_address>"
    },
    "name": "mm_buy_usdc_link"
  }
}

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
`wallet_address`	Yes

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?

No annotations exist, so the description carries the full load. It usefully implies the tool returns a hosted Coinbase page rather than moving funds itself, but it does not state whether any state changes on the deal, whether the link expires, or what the caller gets back.

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 compact sentences with the scope condition front-loaded and no filler. 'Lock it' is slightly cryptic for a first-time caller, which keeps it from a 5.

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 3-required-parameter, no-annotation, no-output-schema tool, the description covers what the tool yields and the next step in the flow. It omits the return shape (URL vs. page), idempotency, and any failure conditions, which are meaningful gaps without annotations.

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%: deal_id and token are documented in the schema, but wallet_address has no schema description. 'Delivered to the given wallet' partly fills that gap by indicating it is the USDC destination, but adds nothing about token sourcing or deal_id format beyond the schema. Baseline 3 fits.

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 concrete action and resource: produce a Coinbase page to buy USDC with a card or Apple Pay, scoped to 'USDC deals on Base', with delivery to the given wallet. That is specific enough to separate it from payment-link or funding-request siblings, though it never names the sibling handling non-USDC deals.

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?

The phrase 'For USDC deals on Base' gives a scope condition, and 'Then lock it with mm_get_funding_request' gives a follow-up step. However, it never says when to prefer mm_get_payment_link or what to do for deals not denominated in USDC, so the agent must infer the boundary.

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?