SimFuse eSIM Storefront

Get plan country coverage

get-plan-coverage

Read-onlyIdempotent

List every country one eSIM plan works in, plus any country of its own region that it leaves out. Use it to answer "does this plan also cover Austria?" for a regional or worldwide plan, where the plan name says a region and the traveller needs the actual list. For a single-country plan the answer is that one country. Ask get-plan instead for the data allowance, validity or price. Read-only.

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-coverage"
  }
}

Input Schema

Name	Required	Description	Default
`plan_id`	Yes	The plan id: a 26-character ULID as returned by list-plans or plan-trip, e.g. "01JVQ2S6D4X8N0RMB7YQZ5K3TA". Slugs and supplier codes are not accepted, and an id must never be invented.

Output Schema

Name	Required	Description
`total`	Yes	How many countries the plan covers.
`countries`	Yes	Every country the plan works in. Match on iso2 to answer "does this cover X?".
`is_worldwide`	Yes	True when the plan is sold as a worldwide bundle.
`region_label`	Yes	The plan's region written for a person, e.g. "Europe". Null for a country plan.
`coverage_type`	Yes	Scope of the plan: one country, a region, or worldwide.
`total_excluded`	Yes	How many countries of the plan's own region it does NOT cover.
`excluded_countries`	Yes	Countries in the plan's own region that it does not cover. Always empty for a country plan and for a worldwide one.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds the useful nuance that output includes both covered countries and countries omitted from a plan's own region, but this is essentially return-value semantics already carried by the output schema. Like the redundant 'Read-only' trailer, it adds limited value beyond structured fields.

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-loads the core behavior in the first sentence, then routes usage and alternative. Nearly every clause earns its place, though the trailing 'Read-only' is redundant with readOnlyHint and could be dropped.

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?

For a single-param read tool with a full output schema and rich annotations, the description supplies everything an agent needs: purpose, usage context, edge-case behavior, and sibling routing. No material gaps remain.

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 single plan_id parameter is thoroughly documented (ULID format, 26 chars, no slugs/supplier codes, never invent an id). The description contributes nothing about plan_id, so the baseline 3 is appropriate.

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?

Names a specific verb and resource ('list every country one eSIM plan works in') and even specifies the exact edge behavior (regional vs single-country plans). It distinguishes itself from its sibling get-plan by naming what get-plan covers instead. An agent can select this without opening either 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?

Gives an explicit use case ('does this plan also cover Austria?' for regional/worldwide plans) and an explicit alternative with its scope ('Ask get-plan instead for the data allowance, validity or price'). The when-to-use and when-not-to-use routing is fully determined.

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

All SimFuse eSIM Storefront tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?