Skip to main content
Glama

Update departure

update_departure
Destructive

Update a departure's seats, status, price, or notes.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the mutation profile is covered structurally. The description adds nothing beyond that: it does not say whether omitted fields are preserved, whether status transitions are constrained, whether cancellation via status is equivalent to cancel_departure, or what permissions are needed for a destructive update.

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?

A single front-loaded sentence with no filler; the terseness is appropriate in form, even though the content is too thin for the tool's complexity.

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, 7-parameter mutation with no output schema and near-zero schema description coverage; the one-line description is far short of what an agent needs to call it safely. The most consequential facts — partial-update semantics, overlap with cancel_departure, and enum meanings — are all missing.

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 14% across 7 parameters, so the description must compensate and does not. It names four updatable fields but adds no semantics: no explanation of the status enum values, no meaning for 'min_to_run', no clarification that business_id is optional for single-business connections (only the schema documents that), and no note that all fields other than departure_id are optional.

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 names a specific verb ('Update') and resource ('a departure') and enumerates the mutable fields (seats, status, price, notes), so an agent knows the operation. Differentiation from siblings is absent though: 'cancel_departure' exists and this tool's status enum includes 'canceled', leaving the boundary between the two ambiguous.

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 guidance on when to prefer this tool over 'cancel_departure' or 'create_departure', no prerequisites, and no statement about partial vs full updates. The agent must infer usage entirely from the name and schema.

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