MM by Escrow MCP

Quote fees

mm_quote

Read-only

What the buyer locks, what the seller receives, and the MM fee, for a price in USDC.

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": {
      "price_usdc": "<price_usdc>"
    },
    "name": "mm_quote"
  }
}

Input Schema

Name	Required	Description
`price_usdc`	Yes	Price in dollars
`fee_paid_by`	No
`payment_rail`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

C2.9/5.0

Behavior3/5

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

The readOnlyHint annotation already tells the agent this is safe and non-mutating. The description adds conceptual output context but does not explain how the quote changes with payment rail or fee allocation, nor any other behavioral constraints.

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?

The definition is a single efficient sentence with no filler. It is front-loaded but uses a sentence fragment and 'MM' jargon that may not be self-explanatory.

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

Completeness2/5

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

For a read-only quote tool with two optional enum parameters and no output schema, the description omits how those parameters alter the quoted amounts. It is not complete enough for confident invocation beyond the simplest single-price call.

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

Parameters2/5

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

Schema description coverage is only 33%, and the description does not compensate. It never explains fee_paid_by's buyer/seller/split choices or payment_rail's usdc/card_or_bank choices, and 'for a price in USDC' may blur the payment-rail distinction.

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 title 'Quote fees' plus the description clearly indicates this returns buyer-locked amount, seller proceeds, and MM fee for a USDC price. The verb is implicit rather than explicit, but the resource and result are specific.

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?

The description gives no explicit when-to-use guidance, prerequisites, or comparison to siblings. An agent can infer it is a pre-deal quote, but that is not stated.

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?