Skip to main content
Glama

Migawari

Accept a quote

accept_quote

Accept a quote. IMPORTANT: this does not confirm execution. The request enters pending_review; a human operator confirms or declines each request individually during the launch phase. No timeline is promised. Poll get_task_status for the outcome. Payment: pay_with 'card' (default, Stripe) or 'jpyc' / 'usdc' to pay in stablecoins on Polygon — the response then carries payment_instructions with the exact amount (including a unique fractional tail that identifies your transfer) and the receiving address.

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": {
      "quote_id": "<quote_id>",
      "access_token": "<access_token>"
    },
    "name": "accept_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
pay_withNoPayment rail: card (Stripe, default), or jpyc / usdc stablecoins on Polygon.
quote_idYes
access_tokenYesThe access_token returned by request_quote.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false) the description discloses the critical behavioral fact that acceptance does not confirm execution, that a human operator reviews each request, and that no timeline is promised. It also explains the payment rails and what the response carries for stablecoin payments (payment_instructions, exact amount with a unique fractional tail, receiving address).

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 most important constraint ('this does not confirm execution') is front-loaded right after the purpose statement, and every sentence carries operational information. The payment sentence is long and dense, but each clause is load-bearing rather than filler.

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?

There is no output schema, so the description bears the return-value burden; it covers the stablecoin case but leaves the card path's response shape (e.g., a task or review identifier to poll with) unexplained. For a mutation tool with a human-review step, the crucial caveats are all present.

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

Parameters4/5

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

With 67% schema coverage and an enum on pay_with, the schema already documents all three parameters reasonably well. The description still adds value by tying pay_with='card' to Stripe as the default and explaining that stablecoin rails change the response shape via payment_instructions, which is not derivable from 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?

The description names a specific verb and resource ('Accept a quote') and immediately qualifies the outcome: the request enters pending_review rather than being executed. It does not explicitly contrast itself with decline_quote or note that request_quote must precede it, so sibling differentiation is only partial.

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?

It gives useful downstream guidance ('Poll get_task_status for the outcome') and conditions on the launch phase, but never says when an agent should choose accept_quote over decline_quote or how to decide. Usage context is implied rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.