AirTreks MCP

Submit a Trip Request (Consultant Handoff)

trip_idea_create

Submit the customer's trip to AirTreks — a human travel consultant takes over from there. Automatically runs plan_route to attach the full routing analysis and carrier recommendations to the trip request, so the consultant starts informed, not cold. Use this when the customer is ready to get a real quote. Requires the customer's name, email, at least 2 cities (3-letter IATA codes), a departure date for every leg, and answers to AirTreks' planning questions — call once without questionsAnswers to receive the current questions to ask.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Customer full name (required — the consultant contacts them by name)
`cabin`	No	Cabin class preference
`dates`	Yes	Departure dates, one per leg (ISO format, e.g. '2026-09-15') — a trip with N cities needs N-1 dates, all required. If the customer is unsure, use their best estimates and set flexibleDates.
`email`	Yes	Customer email address (required)
`notes`	No	Additional notes or special requests from the customer
`phone`	No	Customer phone number
`budget`	No	Budget tier
`cities`	Yes	Ordered list of 3-letter IATA city/airport codes (e.g. ['SFO', 'NRT', 'BKK'])
`source`	No	The AI platform or app this conversation is running in, lowercase (e.g. 'chatgpt', 'claude', 'perplexity'). Only tells AirTreks which channel the request came through — never put customer details here. Omit it if you don't know.
`passengers`	No	Number of passengers (default 1)
`preferences`	No	Travel preferences: 'no-lcc', 'lounge-access', 'short-layovers', 'surface-ok'
`agentContext`	No	Summary of what the AI agent learned about this trip (auto-generated routing analysis, customer preferences discussed, etc.)
`sourceDetail`	No	Finer detail on source, such as the app or integration name (e.g. 'trip-pricer'). Never put customer details here.
`flexibleDates`	No	Are travel dates flexible?
`questionsAnswers`	No	The customer's answers to AirTreks' planning questions, keyed by question name (e.g. {"guidance": "I want expert guidance from humans"}). A JSON-encoded string of the same object is also accepted. Required, but don't guess the questions: call once without this — the response lists the current questions and their options to ask the customer.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 2, 2026

addedInput schema / properties / source

Added value: +{
+  "description": "The AI platform or app this conversation is running in, lowercase (e.g. 'chatgpt', 'claude', 'perplexity'). Only tells AirTreks which channel the request came through — never put customer details here. Omit it if you don't know.",
+  "type": "string"
+}

addedInput schema / properties / sourceDetail

Added value: +{
+  "description": "Finer detail on source, such as the app or integration name (e.g. 'trip-pricer'). Never put customer details here.",
+  "type": "string"
+}

First observedAug 21, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Adds substantial behavior beyond the annotations: it discloses that a human consultant takes over, that plan_route is auto-invoked to attach routing analysis and carrier recommendations, and that a first call without questionsAnswers is a discovery step returning the current questions. This is real side-effect and workflow context the annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false) do not convey.

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 handoff purpose is front-loaded, followed by the auto-plan_route behavior, the trigger condition, and prerequisites. Five sentences with no padding, though the prerequisites and the two-step instruction could be slightly tightened.

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 15-parameter mutation with no output schema, the description covers the workflow, required inputs, and the discovery-call pattern adequately. Minor gaps remain on error handling and what the submission response contains, but the essential callable context is present.

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 baseline is 3, but the description adds value by stating the minimum viable inputs (name, email, at least 2 cities as 3-letter IATA codes, a departure date per leg) and, importantly, the two-step questionsAnswers protocol that the schema only hints at.

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?

States a specific verb and resource ('Submit the customer's trip to AirTreks') and immediately clarifies the handoff to a human consultant, which cleanly separates it from the routing/quoting siblings. An agent can tell this is the terminal booking-intent action rather than a lookup or estimate.

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?

'Use this when the customer is ready to get a real quote' gives clear triggering context, and the requirement list sets expectations for readiness. It stops short of naming explicit alternatives or when-not-to-use conditions, but the internal relationship to plan_route is disclosed.

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

All AirTreks MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Submit a Trip Request (Consultant Handoff)

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources