Skip to main content
Glama

Plan a Multi-City Route

plan_route
Read-only

Lay out a multi-city trip: direction of travel, regions crossed, backtracking, where a surface sector could replace a flight, and how complex the trip is to ticket. Give it your cities. It does not choose airlines and gives no prices - use route_estimate for a price range and trip_idea_create to hand the trip to AirTreks.

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": "plan_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
paxNoNumber of passengers
budgetNoBudget tier the traveler asked for
citiesYesOrdered list of IATA city/airport codes (e.g. ['LAX', 'NRT', 'BKK', 'LIS', 'LAX'])
preferencesNoTravel preferences: '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 — affects carrier selection and fare strategy"New value: +"Budget tier the traveler asked for"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description adds real behavioral context by enumerating the analytical dimensions returned (backtracking, surface sectors, ticketing complexity) and by explicitly bounding scope (no carriers, no pricing). It stops short of describing the shape or granularity of the response, which matters somewhat given there is no output schema.

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?

Three tight sentences: capability first, input instruction second, exclusions and redirects last. Every clause carries information, and the load-bearing scope limits are front-loaded rather than buried at the end.

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, four-parameter analysis tool with full schema coverage and annotations covering safety, the description covers purpose, inputs, output dimensions, and handoff paths, so an agent can select and call it correctly. The only gap is that the returned structure is implied by a list rather than described, which is a minor omission absent an 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 all four parameters including the enum-constrained budget and the preference vocabulary are already documented in the schema. The description only adds the framing that the cities list is the driving input, which is marginal beyond what the schema states. Baseline 3 is appropriate when the schema carries the parameter burden.

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 states a specific verb and resource ("Lay out a multi-city trip") and then enumerates exactly what the layout covers: direction of travel, regions crossed, backtracking, surface-sector substitution, and ticketing complexity. That enumeration distinguishes it from sibling analysis tools like route_validate and route_suggest without the agent needing to open a schema.

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 gives an explicit invocation cue ("Give it your cities") and names two exclusions with the correct redirects: no airline selection, no prices, with route_estimate for a price range and trip_idea_create for handing the trip to AirTreks. The when-not conditions and the alternative tools are both spelled out.

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.