Skip to main content
Glama

create_booking

Create a booking. CRITICAL: Check start/end time year. Do NOT default to 2024. Use 'get_dispatch_context_and_time' to verify "Today". ONE-SHOT: CALCULATE dates yourself from context. Do NOT ask user for ISO strings. ACTION: You MUST output the Booking Confirmation Summary returned by this tool. If this tool is not called, NO booking exists.

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": {
      "validityToken": "<validityToken>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "create_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesEnd time (ISO). Verify YEAR is current.
notesNoOperational notes or remarks
startYesStart time (ISO). Verify YEAR is current.
aircraftIdNoAircraft Registration (e.g. PH-DEMO).
validityTokenYesToken from get_dispatch_context_and_time. REQUIRED.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / aircraftId / description
      Previous value: -"Aircraft Registration (e.g. D-EPUC)."New value: +"Aircraft Registration (e.g. PH-DEMO)."
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses that the tool depends on an externally issued validityToken and that no booking exists unless this call is made, plus that a Booking Confirmation Summary is returned and must be surfaced. It says nothing about conflict/double-booking handling, failure modes, or whether the operation is reversible.

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?

The purpose statement is front-loaded in the first line and the rest is short, directive, and each block addresses a distinct risk (wrong year, asking the user, swallowing the confirmation). The year check is duplicated between the description and the schema field descriptions, and the all-caps shouting adds little.

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 mutation tool with no annotations and no output schema, the description covers the critical gaps: the required token's source, how to derive start/end, and what return value must be relayed to the user. Residual gaps are error behavior, slot-conflict outcomes, and the semantics of the optional aircraftId.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the bar is a baseline 3; the description clears it by adding normative guidance not present in the schema — do not accept user-supplied ISO strings, derive dates from context, and verify the year so it does not default to 2024. The provenance of validityToken is reinforced. It does not explain what happens if the optional aircraftId is omitted.

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?

"Create a booking" is a specific verb + resource, and the surrounding siblings (cancel_booking, find_available_slots, get_my_bookings) make the create-versus-query-versus-cancel split obvious. It never explicitly names an alternative, so it stops short of a 5, but no agent would confuse it with a sibling.

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?

Gives a concrete prerequisite workflow: call get_dispatch_context_and_time first to establish 'today' and obtain the validityToken, and calculate dates yourself rather than interrogating the user. It does not say whether a slot should be checked with find_available_slots first or when to prefer preview_settlement, so exclusions are missing.

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