Skip to main content
Glama

List eSIM destinations

list_esim_destinations
Read-onlyIdempotent

Every country and multi-country region SimOwl sells travel eSIMs for, with the lowest price and the page URL.

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
currencyNoISO 4217 code to quote prices in (USD, EUR, GBP, JPY...). Defaults to EUR when not sold.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description then adds return-value content — that each destination comes with its lowest price and the page URL — which matters because no output schema exists. It does not say how large the result is or whether it is paginated.

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?

One sentence, front-loaded with scope and immediately followed by the payload contents. Nothing is redundant and nothing needs to be skipped over.

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 simple annotated read-only listing tool with one optional parameter, the definition conveys scope and returned fields adequately. Minor omissions are result size, ordering, and whether the catalog is static or changing.

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% on the single currency parameter, including the EUR fallback rule, so the schema does the heavy lifting. The description's mention of 'lowest price' hints that the currency affects the quoted figure but adds no syntax or format detail beyond the schema.

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 resource (every country and multi-country region sold for travel eSIMs) and what each entry carries (lowest price, page URL). It is clearly distinguishable from find_esim_plans or estimate_trip_data in substance, though it never explicitly contrasts itself with them.

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

Usage Guidelines2/5

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

There is no when-to-use statement, no exclusion, and no pointer to an alternative such as find_esim_plans for per-plan detail. At best the agent can infer this is a catalog-browsing call from the resource name alone.

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