Skip to main content
Glama

Cancel departure

cancel_departure
Destructive

Cancel a departure.

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": {
      "departure_id": "<departure_id>"
    },
    "name": "cancel_departure"
  }
}

Input Schema

NameRequiredDescriptionDefault
business_idNoThe id of the business to act on, from list_businesses. Optional when this connection covers a single business.
departure_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2/5.0
Behavior2/5

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

The annotations already flag destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds nothing beyond that: it does not say whether the cancellation is reversible, what happens to bookings attached to the departure, or whether a cancelled departure remains visible to list_departures.

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

Conciseness2/5

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

It is one short sentence with no wasted words, but that is under-specification rather than conciseness. There is nothing front-loaded beyond the bare action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a destructive mutation with no output schema and an undocumented required parameter. Given that complexity, the definition should say at minimum what is destroyed, whether it can be undone, and how to obtain a departure_id; it does none of these.

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 coverage is only 50%: business_id is documented in the schema, but departure_id has no description anywhere. The description does not compensate by explaining where a departure_id comes from (presumably list_departures) or what the business_id fallback means for single-business connections.

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

Purpose2/5

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

"Cancel a departure" only restates the tool name and title with no additional detail. It names a verb and resource, but gives an agent nothing it could not read off the title, and it does not distinguish itself from sibling mutations such as cancel_booking.

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?

There is no when-to-use, when-not-to-use, or prerequisite guidance. The description never mentions the existence of cancellation policies (list_cancellation_policies is a sibling) or whether a departure must be in a particular state before it can be cancelled.

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