Skip to main content
Glama

Preview an airport transfer quote

preview_transfer_quote
Read-only

Calculate a non-binding, non-persisted transfer quote. This tool cannot hold, book, message, cancel, or charge.

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": {
      "pickup": "<pickup>",
      "dropoff": "<dropoff>",
      "datetime_local": "<datetime_local>",
      "passengers": "<passengers>",
      "luggage": "<luggage>",
      "vehicle_class": "<vehicle_class>"
    },
    "name": "preview_transfer_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
marketNoFJ
pickupYes
dropoffYes
luggageYes
childrenNo
passengersYes
route_codeNo
child_seatsNo
distance_kmNo
agent_sourceNo
flight_numberNo
vehicle_classYes
datetime_localYes
quote_currencyNo
agent_session_idNo
customer_preferred_currencyNo

Output Schema

NameRequiredDescriptionDefault
marketYes
statusYes
previewYes
persistedYes
next_actionYes
continue_urlYesSame-site booking form for customer review.
booking_eligible_from_previewYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / continue_url
      Added value: +{
      +  "description": "Same-site booking form for customer review.",
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "market",
      -  "status",
      -  "preview",
      -  "persisted",
      -  "booking_eligible_from_preview",
      -  "next_action"
      -]New value: +[
      +  "market",
      +  "status",
      +  "preview",
      +  "persisted",
      +  "booking_eligible_from_preview",
      +  "continue_url",
      +  "next_action"
      +]
  2. First observed

TDQS

B3.4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description reinforces this with 'non-persisted' and an explicit list of actions it cannot perform. That is useful disambiguation beyond the annotations, though it says nothing about pricing validity windows, error conditions, or market/currency behavior.

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?

Two sentences, front-loaded with the core action and followed by the constraint boundary. No filler and nothing redundant with the schema or annotations.

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?

An output schema exists, so return values need no explanation, but a 16-parameter request with six required fields and zero schema descriptions demands more than a scope disclaimer. An agent gets no guidance on location field selection, date/time format, or currency semantics, which are the main sources of incorrect calls here.

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 0% across 16 parameters, yet the description mentions none of them. It gives no hint about how pickup/dropoff locations must be shaped (airport vs hotel vs address with different identifier fields), how vehicle_class values relate to passenger/luggage counts, or what quote_currency versus customer_preferred_currency means.

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 and resource ('Calculate ... transfer quote') and the qualifiers 'non-binding, non-persisted' make clear this is a price-preview operation. The word 'transfer' distinguishes it from siblings like preview_rental_quote and preview_private_driver_quote, though it does not explicitly name those alternatives.

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?

It establishes the key usage boundary by stating the tool 'cannot hold, book, message, cancel, or charge,' which tells the agent this is for quoting only and that any commitment step belongs elsewhere. However, no sibling is named and no positive guidance is given about when a transfer quote is the right request versus a rental or private-driver quote.

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