Skip to main content
Glama

Build a Custom Segmented Route

custom_route_build
Read-only

Break a complex multi-city itinerary into individually-ticketable segments with carrier recommendations. Handles routes that don't fit alliance fare rules — mixed carriers, LCCs, Gulf bridge connections, surface sectors. This is how AirTreks consultants build 90% of itineraries. Use this for any route with 4+ stops, backtracking, or region combinations that alliance fares can't cover.

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": {
      "cities": "<cities>"
    },
    "name": "custom_route_build"
  }
}

Input Schema

NameRequiredDescriptionDefault
paxNoNumber of passengers
budgetNoBudget tier the traveler asked for
citiesYesOrdered list of IATA city/airport codes (e.g. ['LAX', 'NRT', 'BKK', 'CMB', 'NBO', 'LIS', 'LAX'])
preferencesNoPreferences: 'no-lcc', 'lounge-access', 'short-layovers', 'surface-ok'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / budget / description
      Previous value: -"Budget tier: 'budget' prioritizes LCCs, 'business' prioritizes J-class product quality"New value: +"Budget tier the traveler asked for"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: it explains what the tool handles (mixed carriers, LCCs, Gulf bridge connections, surface sectors) and what it produces (individually-ticketable segments plus carrier recommendations). It doesn't disclose latency, pricing freshness, or failure modes, so it isn't a 5.

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?

Four tight sentences, front-loaded with purpose, then scope, then the decision rule. The only near-wasteful line is 'This is how AirTreks consultants build 90% of itineraries', which is credibility-building rather than operational, but it occupies just one sentence.

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 read-only planning tool with no output schema and fully described parameters, the description supplies the domain framing an agent needs: what kinds of routes qualify and what the result conceptually is. It leaves the actual return shape (segment objects, carrier fields) and any availability/pricing caveats unstated, a minor gap given there is no output schema.

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%, so the schema already documents pax, budget, cities, and preferences, including the enumerated preference values and the ordered IATA-code format. The description adds no parameter-level meaning beyond that baseline; its mention of '4+ stops' loosely maps to the cities array but gives no additional semantics.

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 opens with a specific verb and resource: 'Break a complex multi-city itinerary into individually-ticketable segments with carrier recommendations.' It also clearly distinguishes the tool from fare-based siblings by scoping it to routes that 'don't fit alliance fare rules', so an agent can tell it apart from plan_route or itinerary_quote without opening either schema.

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?

Usage criteria are concrete and testable: 'Use this for any route with 4+ stops, backtracking, or region combinations that alliance fares can't cover.' It also implicitly excludes alliance-fare-eligible routes. It stops short of naming a specific sibling to use instead for simple routes, which keeps it below a 5.

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.