Skip to main content
Glama

List Simcardo eSIM destinations

list_esim_destinations
Read-onlyIdempotent

Discover countries, territories and regional/global packages. Coverage-only territories have no dedicated storefront. Returns active languages, counts, localized names and canonical links where available. Paginate with next_after_market. Use quote_travel_esim for dates and hotspot.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_esim_destinations"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeNoall
languageNoStorefront language for localized destination names, price display and links. Reply to the traveler in their language.en
page_sizeNo
after_marketNoCopy next_after_market from the previous page, with the same scope.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, open-world behavior, yet the description adds real value beyond them: what the response contains (active languages, counts, localized names, canonical links), the coverage-only territory caveat, and how paging works. A rate-limit or freshness note would have earned a 5.

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?

Five short sentences, front-loaded with what the tool surfaces, then caveats, then return shape, then paging, then the routing hint. No filler and no repetition of the title.

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?

With no output schema, the description correctly spends its words describing the response payload and pagination token, which is the right allocation. The remaining shortfall is the undocumented scope enum, the parameter that most changes what comes back.

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 50%: language and after_market are documented in the schema. The description reinforces pagination by naming the response field next_after_market, though it never mentions the input parameter as after_market, and it leaves scope (all/country/package) and page_size entirely unexplained. That is the most consequential gap for a filtered-list tool.

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?

"Discover countries, territories and regional/global packages" gives a concrete verb plus the exact resource set, so the agent knows this is the destination catalog. It also hints at the scope split (country vs package). It does not distinguish itself from list_esim_plans, only from quote_travel_esim, which keeps it from a 5.

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?

Clear routing away from this tool for pricing: "Use quote_travel_esim for dates and hotspot," plus an explicit pagination instruction and the note that coverage-only territories lack a storefront. No guidance is given on when this tool should be chosen over list_esim_plans, so the exclusion set is incomplete.

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