Skip to main content
Glama

Destination plans and prices

list_destination_plans
Read-only

Lists the eSIM plans that Horizon sells now for one destination (a country or a region): the data amount, the number of days, the unlimited flag, the price in EUR and a link to each plan's page on horizonesim.com. Takes the destination's English name or slug, for example "Netherlands", "United States" or "europe". Prices and links are current when returned; the plan page shows the final price before purchase.

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": {
      "destination": "<destination>"
    },
    "name": "list_destination_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault
destinationYesThe English name or the slug of a country or region, for example "Netherlands", "usa", "balkans" or "europe".

Output Schema

NameRequiredDescriptionDefault
plansYes
currencyYes
destinationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/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 genuinely useful behavioral context — prices and links are current at return time and the final price must be confirmed on the plan page — but says nothing about behavior when a destination is invalid or has no plans, and the live-data implication sits slightly awkwardly with openWorldHint=false.

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?

Front-loaded with the core purpose in the opening clause, then a scoping sentence and a price caveat; there is no filler. The mid-sentence enumeration of output fields is somewhat redundant given an output schema exists, but it is compact and aids tool selection.

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 one-parameter read-only lookup with an output schema, the definition supplies the essentials: what is returned, what the destination argument accepts, and a caveat about price currency. The only meaningful omissions are failure/empty-result behavior and any ordering or result-count expectations.

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% and the single parameter already documents "English name or the slug of a country or region" with examples ("usa", "balkans", "europe"). The description restates the same rule with a slightly different example set ("Netherlands", "United States", "europe"), adding marginal clarity on full-name vs slug but no new syntax or normalization rules.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ("Lists") and resource ("eSIM plans that Horizon sells now for one destination") and enumerates the returned attributes (data amount, days, unlimited flag, EUR price, plan link). It implicitly separates itself from get_destination_coverage by emphasizing prices and purchasable plans, but never names a sibling or states the boundary explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied by "for one destination (a country or a region)" and by the closing note that the plan page shows the final price before purchase, which tells an agent to treat returned prices as indicative. There is no explicit when-to-use/when-not guidance relative to search_destinations or get_destination_coverage, and no mention of what to do for an unknown destination.

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