Skip to main content
Glama

Migawari

Decline a quote

decline_quote
Destructive

Decline a quote and close it. Declining a quote you have not accepted is free of charge; no handling fee applies.

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": "decline_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo
quote_idYes
access_tokenYesThe access_token returned by request_quote.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, and 'close it' is consistent with that destructive profile rather than contradicting it. The description adds a genuinely useful cost detail (free unless already accepted, no handling fee), which hints at consequences of the transition, but it leaves out what 'close' does to the related task, whether the action is reversible, or any permission requirements.

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 short sentences, front-loaded with the action and effect, with no filler. The second sentence earns its place by carrying the one non-obvious behavioral fact, though the phrasing is slightly clunky ('Declining a quote you have not accepted').

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?

There is no output schema, so the description needn't explain return values, and the safety profile is covered by annotations. However, for a destructive, closing operation with an undocumented optional 'reason' parameter, an agent is left guessing whether a reason is expected, what happens to downstream state, and what a successful decline returns.

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% — access_token is documented as coming from request_quote, but quote_id and reason have no schema descriptions and the description adds nothing about them. In particular, the optional 'reason' parameter, which apparently feeds a business process, is never explained in either place, so the description fails to compensate for the coverage gap.

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 resource — 'Decline a quote' — plus the side effect 'and close it'. It is clearly distinguishable from accept_quote and request_quote by the verb alone, though it never explicitly names the alternative path for an agent that wants to accept instead.

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?

'Declining a quote you have not accepted is free of charge' implies a precondition, but it is framed as a pricing note rather than a rule. There is no statement of when to choose decline over accept, no prerequisite about quote state or required permissions, and no exclusion for quotes already accepted.

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.