Skip to main content
Glama

Plan eSIMs for a multi-country trip

plan_trip
Read-only

Use this when one trip visits SEVERAL countries, e.g. "Italy then Greece", "two weeks in Japan and Korea". Compares one GlobalPass regional pass that works in all of them with a separate plan per country, and returns both with prices and links to buy. For a single country call search_plans.

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": {
      "stops": "<stops>"
    },
    "name": "plan_trip"
  }
}

Input Schema

NameRequiredDescriptionDefault
stopsYesEvery country of the trip, with the days spent in each when known.
currencyNoCurrency for prices. Defaults to PLN for Polish and EUR otherwise.
languageNoThe traveller's language: en, pl or ru.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description only needs to add context. It does add real value: it tells the agent the result is a comparison of two options, both with prices and buy links, i.e. two distinct pricing proposals rather than one answer. It does not mention whether the comparison is always complete, how missing days are handled, or any failure behavior, but the additions are substantive.

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 short sentences, front-loaded with the triggering condition, then the behavior, then the alternative. The embedded examples resolve ambiguity about what counts as multi-country without extra prose. No filler or repeated information from the title or schema.

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

Completeness3/5

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

For a read-only tool with a fully described schema and no output schema, the description covers purpose, inputs, and the returned shape at a high level, which is close to sufficient. What it omits is meaningful: with no output schema, the agent learns nothing about the structure of the returned comparison (how the two options are labeled, whether prices are per-country or total, currency formatting) or about partial results when a country is unsupported.

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%, so the baseline is 3; the description earns a bump by explaining that the stops list means "every country of the trip" and framing what each stop contributes to the comparison. Currency and language defaults are already documented in the schema and are not duplicated, which is appropriate rather than a gap.

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 concrete selection condition ("one trip visits SEVERAL countries") plus worked examples, then states the comparison performed: one GlobalPass regional pass versus a separate plan per country, returned with prices and links. It also names the sibling search_plans and the condition (single country) that routes there instead, so an agent can distinguish the two without opening schemas.

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?

Explicit when-to-use is given (multi-country trip, with two illustrative examples) and an explicit alternative with its own trigger condition: "For a single country call search_plans." No exclusions or prerequisites are left implicit beyond that, and the multi-country condition is the only plausible boundary for this family of tools.

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