Skip to main content
Glama

Migawari

Cancel a quote or task

cancel_task
Destructive

Cancel a quote that has not been accepted yet, or a task that is in pending_review, confirmed, or in_progress. Cancelling an unaccepted quote is free. If payment was already made for a task, the quote fee (JPY 2,200) remains charged per the fee model, and the operator follows up about a refund of the remainder via the record messages.

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": {
      "id": "<id>",
      "access_token": "<access_token>"
    },
    "name": "cancel_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesquote_id (q_…) or task_id (t_…).
reasonNo
access_tokenYesThe access_token returned by request_quote.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, and the description goes well beyond that by disclosing the financial consequence: free for unaccepted quotes, JPY 2,200 quote fee retained if payment was made, with a partial refund handled out-of-band via record messages. That is exactly the cost/reversibility context an agent needs before invoking a destructive tool.

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?

Three sentences, front-loaded with eligibility before the cost caveats, which is the right ordering for a destructive action. The fee sentence is dense but every clause carries decision-relevant information; no 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?

For a destructive, no-output-schema tool this covers eligibility, cost, and post-cancellation follow-up well. Residual gaps are the undocumented 'reason' parameter and no indication of what the call returns or whether cancellation is reversible once executed.

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%: id and access_token are documented in the schema, while 'reason' has no description anywhere. The description adds no meaning for any parameter, so it neither compensates for the gap nor detracts. Baseline 3 is appropriate.

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 (cancel) plus both target resources (quote, task) and pins down the exact eligible states (unaccepted quote; pending_review, confirmed, in_progress task). An agent can tell immediately whether a given record is cancellable. It does not name disambiguating siblings such as decline_quote, so it stops short of 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is gated by explicit preconditions: only unaccepted quotes and tasks in three named statuses. That is clear context for when to call it. It gives no explicit when-not guidance or named alternative (e.g., decline_quote for an offered quote), leaving the sibling boundary to inference.

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.