Skip to main content
Glama

Submit a Trip Request (Consultant Handoff)

trip_idea_create
Destructive

Submit the customer's trip to AirTreks as a complete, structured trip request - a human travel consultant takes over from there. Ask the traveler for everything before calling, never guess or fill in defaults: name, email, the cities in order (3-letter IATA codes), a departure date for every leg, number of passengers, cabin (economy, premium or business), and their answers to AirTreks' planning questions. Also ask about budget, flexible dates, preferences and anything else the consultant should know. Call once without questionsAnswers to receive the current planning questions to put to the traveler.

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": {
      "email": "<email>",
      "name": "<name>",
      "cities": "<cities>",
      "dates": "<dates>",
      "passengers": "<passengers>",
      "cabin": "<cabin>"
    },
    "name": "trip_idea_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesCustomer full name (required — the consultant contacts them by name)
cabinYesCabin class (required — ask the customer, there is no default)
datesYesDeparture dates, one per leg (ISO format, e.g. '2026-09-15') — a trip with N cities needs N-1 dates, all required. Ask the customer; never invent dates. If they only know roughly, use their stated estimates and set flexibleDates.
emailYesCustomer email address (required)
notesNoAdditional notes or special requests from the customer
phoneNoCustomer phone number
budgetNoBudget tier
citiesYesOrdered list of 3-letter IATA city/airport codes (e.g. ['SFO', 'NRT', 'BKK'])
sourceNoThe 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.
passengersYesNumber of passengers (required — ask the customer, there is no default)
preferencesNoTravel preferences: 'no-lcc', 'lounge-access', 'short-layovers', 'surface-ok'
agentContextNoSummary of what the AI agent learned about this trip (auto-generated routing analysis, customer preferences discussed, etc.)
sourceDetailNoFiner detail on source, such as the app or integration name (e.g. 'trip-pricer'). Never put customer details here.
flexibleDatesNoAre travel dates flexible?
questionsAnswersNoThe customer's answers to AirTreks' planning questions, keyed by question name (e.g. {"guidance": "I want expert guidance from humans"}). The answers must come from the customer — never pick one yourself. 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.

  1. Changed11 schema fields changed
    • addedInput schema / properties / agentContext / maxLength
      Added value: +4000
    • addedInput schema / properties / cities / items / maxLength
      Added value: +8
    • addedInput schema / properties / cities / maxItems
      Added value: +14
    • addedInput schema / properties / dates / items / maxLength
      Added value: +10
    • addedInput schema / properties / dates / maxItems
      Added value: +14
    • addedInput schema / properties / email / maxLength
      Added value: +254
    • addedInput schema / properties / name / maxLength
      Added value: +100
    • addedInput schema / properties / notes / maxLength
      Added value: +2000
    • addedInput schema / properties / phone / maxLength
      Added value: +40
    • addedInput schema / properties / preferences / items / maxLength
      Added value: +40
    • addedInput schema / properties / preferences / maxItems
      Added value: +10
  2. Changed8 schema fields changed
    • changedInput schema / properties / cabin / description
      Previous value: -"Cabin class preference"New value: +"Cabin class (required — ask the customer, there is no default)"
    • changedInput schema / properties / dates / description
      Previous value: -"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."New value: +"Departure dates, one per leg (ISO format, e.g. '2026-09-15') — a trip with N cities needs N-1 dates, all required. Ask the customer; never invent dates. If they only know roughly, use their stated estimates and set flexibleDates."
    • changedInput schema / properties / passengers / description
      Previous value: -"Number of passengers (default 1)"New value: +"Number of passengers (required — ask the customer, there is no default)"
    • addedInput schema / properties / passengers / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / passengers / minimum
      Added value: +1
    • changedInput schema / properties / passengers / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / questionsAnswers / description
      Previous value: -"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."New value: +"The customer's answers to AirTreks' planning questions, keyed by question name (e.g. {\"guidance\": \"I want expert guidance from humans\"}). The answers must come from the customer — never pick one yourself. 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."
    • changedInput schema / required
      Previous value: -[
      -  "email",
      -  "name",
      -  "cities",
      -  "dates"
      -]New value: +[
      +  "email",
      +  "name",
      +  "cities",
      +  "dates",
      +  "passengers",
      +  "cabin"
      +]
  3. Changed2 schema fields changed
    • 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"
      +}
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare this as a non-read-only, open-world, non-idempotent, destructive operation. The description adds valuable context about the consultant handoff, the need for complete traveler input, and the two-step question-answer workflow, though it does not explain what happens after submission or how duplicate submissions are handled.

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 description is front-loaded with the purpose and then gives actionable collection instructions. It is somewhat long and repeats schema details, but every sentence has a practical use for an agent preparing the submission.

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 complex write tool with 15 parameters and no output schema, the description covers the key workflow: collecting complete traveler information, avoiding guesses, and discovering planning questions first. It is mostly complete, though it does not describe the successful submission response or follow-up behavior from the consultant.

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 description coverage is 100%, so the schema already documents all 15 parameters in detail. The description mostly restates the same requirements, such as IATA codes, per-leg dates, cabin choices, and the questionsAnswers flow, adding little parameter-level meaning beyond the schema.

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 and resource: submit the customer's trip to AirTreks as a complete structured trip request, with a human consultant taking over. This clearly distinguishes it from the sibling route/fare/planning tools.

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?

It gives explicit workflow guidance: ask the traveler for everything before calling, never guess or use defaults, and call once without questionsAnswers to retrieve the current planning questions. It does not explicitly name sibling alternatives or when not to submit, but the usage context is clear.

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.