Skip to main content
Glama

Request a charter booking

request_booking
Destructive

Submit a charter flight booking request to SkyAccess. This sends the traveler's name, email and trip details (route, date, passengers and any notes) to SkyAccess so a specialist can follow up. A SkyAccess specialist will follow up with the requester by email shortly to confirm availability and pricing. No payment is taken and no booking is created: this only starts the enquiry. If an operator cancels a paid booking, SkyAccess notifies the customer and a specialist starts sourcing a replacement aircraft on the same route; if nothing suits, the customer chooses a full refund or flight credit. Human support is available 24/7 at +1 424-374-3411. Privacy policy: https://skyaccess.com/privacy

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": {
      "origin": "<origin>",
      "destination": "<destination>",
      "departureDate": "<departureDate>",
      "passengers": "<passengers>",
      "name": "<name>",
      "email": "<email>"
    },
    "name": "request_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull name of the requester (required)
emailYesEmail address of the requester (required). A specialist will reply here.
notesNoOptional notes or special requests (e.g. catering, pet, preferred aircraft)
originYesDeparture city or airport (required), e.g. "Los Angeles" or "LAX"
passengersYesNumber of passengers (required)
destinationYesArrival city or airport (required), e.g. "Miami" or "KMIA"
departureDateYesDeparture date in ISO format (required), e.g. "2026-08-15"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / departureDate / description
      Previous value: -"Departure date in ISO format (required) — e.g. \"2026-08-15\""New value: +"Departure date in ISO format (required), e.g. \"2026-08-15\""
    • changedInput schema / properties / destination / description
      Previous value: -"Arrival city or airport (required) — e.g. \"Miami\" or \"KMIA\""New value: +"Arrival city or airport (required), e.g. \"Miami\" or \"KMIA\""
    • changedInput schema / properties / email / description
      Previous value: -"Email address of the requester (required) — a specialist will reply here"New value: +"Email address of the requester (required). A specialist will reply here."
    • changedInput schema / properties / origin / description
      Previous value: -"Departure city or airport (required) — e.g. \"Los Angeles\" or \"LAX\""New value: +"Departure city or airport (required), e.g. \"Los Angeles\" or \"LAX\""
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The description usefully discloses that PII (name, email, trip details) is transmitted to a third party and that a specialist replies by email. But annotations declare idempotentHint=false and destructiveHint=true, and the description never warns that repeat submissions create duplicate requests or that a record is written server-side; 'no booking is created' could even read as reassuring in a way that conflicts with destructiveHint=true.

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?

The first two sentences are front-loaded and on point, but roughly half the text covers operator cancellation, refunds vs. credit, a 24/7 phone number and a privacy URL – none of which help an agent decide to call or how to fill the parameters.

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 7-parameter write with no output schema and no annotations on response shape, the description explains what is sent, what happens next, and that no payment occurs. Only the duplicate-submission/retry behaviour and error handling are missing.

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

Parameters3/5

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

Schema coverage is 100% and every field is already documented, so the description's parenthetical recap (route, date, passengers, notes) adds no new semantics. Baseline 3 applies since the schema carries the burden.

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 first sentence names a specific verb and resource ('Submit a charter flight booking request to SkyAccess') and 'this only starts the enquiry' clarifies the scope of the action. It doesn't name any sibling such as booking_handoff or get_charter_estimate, so the agent must still infer which is the right entry point.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'no payment / no booking is created' line tells the agent this is an enquiry, not a confirmed reservation, which is genuine usage guidance. However, it never states when to prefer get_charter_estimate (pricing first) or booking_handoff (confirming a booking), so routing among siblings remains implied rather than explicit.

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.