Skip to main content
Glama

stopover-planner

by com.stopovercity

search_stopover_itineraries

Find complete multi-day stopover itineraries between two cities: an outbound leg, 1 to 7 days in an intermediate hub city, then the onward leg, priced as one trip from live Google Flights data (GBP) with a booking link on every leg. One call evaluates dozens of hub cities and date splits. Runs as a background job: returns a jobId immediately; poll get_job_result every few seconds until status is done.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
originYesOrigin city or airport, e.g. "London"
nonstopNoNonstop legs only (default true)
destinationYesFinal destination, e.g. "Tokyo"
layoverDaysNoDays to spend in the hub city (default 3)
deadlineDatesYesLatest arrival date(s) at the destination, YYYY-MM-DD. 1 to 31 dates per call; must be real calendar dates (2026-02-30 is rejected).

TDQS

A4.9/5.0
Behavior5/5

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

No annotations provided, but description fully discloses behavioral traits: background job returns jobId, evaluates dozens of hub cities and date splits, pricing in GBP, and booking link on each leg. No contradictions.

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, no wasted words. First sentence conveys core functionality, second adds operational details. Perfectly front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given complexity (multi-city, background job, 5 parameters), description covers all key aspects: purpose, pricing, booking link, and background job polling. No output schema, but explains jobId and polling, so complete for agent invocation.

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%, but description adds context: intermediate hub city, 1-7 days (matches layoverDays), and that it searches multiple hub cities and date splits, which enriches agent understanding.

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 clearly states the tool's purpose: finding multi-day stopover itineraries between two cities, priced as one trip with booking links. It distinguishes from siblings like search_flights (likely direct flights) and get_job_result (polling).

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?

Explicitly describes when to use (for stopover itineraries) and mentions background job behavior with polling via get_job_result. Implicitly differentiates from direct flight searches.

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

All stopover-planner toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool serves a distinct purpose: background job polling, country-wide search, worldwide exploration, synchronous route search, and stopover itinerary generation. No overlap in functionality.

Naming Consistency5/5

All tools use snake_case with consistent verb_noun pattern: search_* for queries and get_job_result for polling. The naming is predictable and clear.

Tool Count5/5

Five tools is well-scoped for a flight search and stopover planner server. Each tool adds unique value without redundancy or unnecessary complexity.

Completeness4/5

The tool set covers core flight search needs (specific routes, country-wide, worldwide, stopovers) with both synchronous and asynchronous modes. Minor gaps like multi-origin search or advanced filters are beyond the stated purpose.

Resources