Skip to main content
Glama

Create departure

create_departure
Destructive

Create a departure with seats, minimum to run, price, and decision date.

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": {
      "activity_id": "<activity_id>",
      "starts_on": "<starts_on>"
    },
    "name": "create_departure"
  }
}

Input Schema

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

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 write/destructive profile is covered structurally. The description adds nothing beyond that: it does not say what happens if min_to_run is never reached, whether decision_on must precede starts_on, or what a successful call returns. The phrase "minimum to run, and decision date" hints at the business logic but does not explain it.

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 or repetition. It is efficient, though its brevity is partly the source of the missing detail rather than a virtue.

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?

For an eight-parameter creation tool with no output schema and near-zero schema description coverage, one sentence is far from sufficient. An agent cannot confidently populate min_to_run, decision_on, price_cents, or notes from this definition alone.

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 13% (only business_id is documented in the schema), so the description carries the burden and largely fails. It echoes four field names in prose but adds no units, formats, defaults, or relationships (e.g., price_cents is cents, decision_on versus starts_on ordering), leaving half the parameters undocumented anywhere.

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 uses a specific verb ("Create") on a specific resource ("departure") and names the key domain fields (seats, minimum to run, price, decision date). It is clearly distinguishable from siblings such as update_departure or cancel_departure, though it does not explicitly say so.

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 use this tool versus alternatives, no prerequisites (e.g., the departure must be attached to an existing activity), and no exclusions. The reader must infer that this is the creation counterpart to update_departure purely from the verb.

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