Skip to main content
Glama

Stopover

Get a saved Stopover plan

get_plan
Read-onlyIdempotent

Looks up a Stopover trip plan by its plan id or flystopover.com plan link and returns the same summary plan_trip gives: the order, dates, total per person, each leg with booking links, and the plan page link. Read only: it never starts a new search. When the plan is still being priced it waits up to a minute for it.

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": {
      "plan_id": "<plan_id>"
    },
    "name": "get_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYesA Stopover plan id (16 letters and digits) or a full plan link like https://flystopover.com/plan/<id>.

Output Schema

NameRequiredDescriptionDefault
demoNo
legsNo
modeNo
notesNo
orderNo
staysNo
statusYes
messageNo
plan_idNo
end_dateNo
plan_urlNo
priced_atNo
travelersNo
fare_basisNo
start_dateNo
start_daysNo
alternativesNo
per_person_usdNo
group_total_usdNo
saving_vs_typed_order_usdNo
typed_order_per_person_usdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive traits, so the bar is lower, but the description still adds real signal: it blocks up to a minute while pricing completes and it discloses the return shape with lookups. Missing is what happens on an unknown or expired id, the main failure mode an agent would need to anticipate.

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: action and return first, safety second, edge-case timing last. Every sentence carries distinct information and nothing is repeated.

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?

Even with an output schema present, the description summarizes the return payload, discloses the pricing wait, and states the read-only boundary. Nothing an agent needs in order to select and invoke this tool correctly is missing.

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%, and the schema already explains that plan_id accepts a 16-char id or a full plan link. The description restates the same dual format without adding validation or format detail beyond it, so the baseline 3 applies.

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 ("looks up a Stopover trip plan by its plan id or ... plan link") and distinguishes it from the sibling by saying it returns the same summary plan_trip gives. An agent can tell exactly what it does and what it returns.

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?

"Read only: it never starts a new search" implicitly routes new searches to plan_trip, and the plan_trip comparison clarifies the shared output. It stops short of an explicit "use plan_trip when you have no plan yet" instruction, so the alternative is implied rather than stated.

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.

Resources