Skip to main content
Glama

skyaccess

by com.skyaccess

Get the booking link for an empty leg flight

booking_handoff
Read-onlyIdempotent

Return the SkyAccess booking page link for a specific empty leg flight, for handing to a customer so they can review and book it themselves. This is READ-ONLY: it does not create, hold, modify or cancel any booking, and no booking exists until the customer completes it on the page. Use request_booking instead if the customer wants a specialist to contact them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
flightIdYesThe flight id returned in the `flightId` field of a search_empty_legs result

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

The description goes beyond the readOnlyHint and destructiveHint annotations by explicitly stating that it does not create, hold, modify, or cancel any booking, and that no booking exists until the customer completes it. This clarifies the side-effect boundary clearly for an agent.

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

Conciseness5/5

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

The description is compact: it states what is returned, the read-only safety property, and the key alternative in three focused sentences. No filler or redundant information is present.

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

Completeness5/5

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

For a simple one-parameter, read-only tool with no output schema, the description provides everything an agent needs: the output type, the use case, the safety semantics, and the alternative tool. Nothing critical is 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?

The input schema already documents the only parameter, flightId, with a clear description referencing search_empty_legs results. The tool description adds little beyond calling it 'a specific empty leg flight,' so it relies appropriately on the schema's 100% coverage.

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

Purpose5/5

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

The description uses a specific verb ('Return') and names the exact resource ('the SkyAccess booking page link') and target ('a specific empty leg flight'). It clearly distinguishes this tool from the sibling 'request_booking' by outlining its self-service purpose.

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

Usage Guidelines5/5

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

It explicitly states when to use the tool: when handing a link to a customer for self-review and booking. It also gives a direct alternative instruction: 'Use request_booking instead if the customer wants a specialist to contact them.' This makes the selection logic unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All skyaccess toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation4/5

search_empty_legs, get_flight, and booking_handoff all return booking links, so booking_handoff overlaps somewhat with get_flight's existing link output. However, each tool's focus (multi-result search, single-flight detail, customer handoff link) is generally clear from the descriptions.

Naming Consistency4/5

Four tools follow a clear verb_noun pattern: search_empty_legs, get_flight, get_charter_estimate, and request_booking. booking_handoff breaks this pattern as a noun-led compound, but the naming remains readable and only mildly inconsistent.

Tool Count5/5

Five tools is well-scoped for this private aviation domain: flight search, flight detail, charter pricing, and two distinct booking paths. Each tool serves a meaningful step in the workflow without unnecessary overlap or bloat.

Completeness4/5

The set covers the core workflows: discovering empty-leg flights, reviewing a specific flight, handing off a booking link, estimating charter prices, and submitting charter requests. Missing status or cancellation endpoints for in-progress requests are minor gaps since specialist follow-up happens outside the server.

Resources