Skip to main content
Glama

decline_quote

Decline a quote and close it. The quote fee (JPY 2,200) remains charged; 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.3/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 disclosure burden, and it does add real value by stating the JPY 2,200 quote fee is still charged and no handling fee applies. However, it omits whether closing is irreversible, what state the quote must be in, and what the call returns, leaving material behavioral gaps for a terminal-state mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the action front-loaded and the cost consequence immediately after. There is no filler and every clause conveys something the agent can act on.

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 mutation tool with no annotations, no output schema, and low parameter coverage, the description covers the key financial outcome but not the quote-state precondition, irreversibility, or expected response. It is adequate but leaves an agent guessing about failure modes.

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 in the schema, but quote_id and reason are undocumented there. The description adds no meaning to any parameter, not even clarifying that reason is an optional free-text explanation attached to the decline.

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 gives a specific verb and resource ("Decline a quote") plus a scope statement ("close it"), so the action is unambiguous. It does not explicitly contrast itself with the sibling accept_quote or state the state prerequisite, which keeps it below a 5.

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?

Usage is only implied by the verb; there is no statement of when to decline versus accept, nor any precondition such as the quote being in a pending state. The financial note (fee remains charged) is decision-relevant but is framed as a consequence, not as routing guidance.

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.

Resources