Skip to main content
Glama

Cancel delivery

cancel_delivery
Destructive

Free before a driver is assigned; a cancellation fee after assignment; not possible after pickup.

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": {
      "delivery_id": "<delivery_id>"
    },
    "name": "cancel_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo
delivery_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds information annotations cannot express: a monetary fee is charged once a driver is assigned, and the operation becomes impossible after pickup — high-value consequences for the caller.

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 compact clauses in state order (before assignment / after assignment / after pickup), front-loaded with zero filler. It is terse to the point of omitting the basic action statement, but nothing written is wasted.

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?

The critical risk (fee) and hard limit (post-pickup) are covered, but for a destructive, non-idempotent mutation with no output schema and 0% param documentation, gaps remain: refund/charge handling, effect on an in-progress delivery, and the role of reason are all unaddressed.

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 0% and neither of the two parameters is mentioned. The description does not say that delivery_id selects the target, nor whether reason is required to waive the fee or is simply recorded — meaning that matters because reason is the only optional param on a fee-bearing operation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The text conveys the cancellation lifecycle but never states the action in verb+resource form ("Cancels a delivery by ID"). An agent must infer from the word "cancellation" and the title that this is the cancellation tool; it is not explicitly distinguished from siblings like update_delivery or confirm_delivery.

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?

It gives real when/when-not conditions: allowed and free before driver assignment, allowed with a fee after assignment, and explicitly not possible after pickup. It stops short of routing to alternatives (e.g. what to do when cancellation is refused), but the eligibility boundaries are clear.

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.