SimFuse eSIM Storefront

List eSIM destinations

list-destinations

Read-onlyIdempotent

Find the countries SimFuse sells eSIMs for, with the cheapest plan price ("from" price) for each in the currency you ask for. Start here when someone names a place: it turns "Portugal" into the two-letter country code the other tools take, and shows what that destination starts at. For one destination, follow it with list-plans; for a trip covering two or more countries, use plan-trip instead. Read-only, and it answers from the SimFuse catalog alone.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Optional. Maximum destinations to return, 1 to 300. Defaults to 300, which is the whole list.
`search`	No	Optional. Match destinations by name, ISO 3166-1 alpha-2 or alpha-3 code, case-insensitively. A partial name works: "port" matches Portugal. Omit to list every destination.
`currency`	No	Optional. ISO 4217 three-letter code the "from" prices are quoted in, e.g. "USD", "EUR", "GBP". Defaults to EUR. An unknown code falls back to EUR rather than failing.

Output Schema

TableJSON Schema

Name	Required	Description
`total`	Yes	How many destinations matched, before `limit` was applied.
`currency`	Yes	ISO 4217 code every from_price_cents below is quoted in, e.g. "EUR".
`returned`	Yes	How many destinations are in this response.
`destinations`	Yes	The matching destinations. Empty when nothing matched.

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedSep 11, 2026

changedInput schema / properties / currency / description

Previous value: -"Three-letter currency code for the \"from\" prices (e.g. \"USD\", \"EUR\"). Defaults to EUR."New value: +"Optional. ISO 4217 three-letter code the \"from\" prices are quoted in, e.g. \"USD\", \"EUR\", \"GBP\". Defaults to EUR. An unknown code falls back to EUR rather than failing."

addedInput schema / properties / currency / maxLength
```
Added value: +3
```
addedInput schema / properties / currency / minLength
```
Added value: +3
```

changedInput schema / properties / limit / description

Previous value: -"Maximum destinations to return, 1-300. Defaults to 300."New value: +"Optional. Maximum destinations to return, 1 to 300. Defaults to 300, which is the whole list."

addedInput schema / properties / limit / maximum
```
Added value: +300
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

changedInput schema / properties / search / description

Previous value: -"Optional. Match destinations by name or country code, case-insensitively. A partial name works (\"port\" matches Portugal)."New value: +"Optional. Match destinations by name, ISO 3166-1 alpha-2 or alpha-3 code, case-insensitively. A partial name works: \"port\" matches Portugal. Omit to list every destination."

addedInput schema / properties / search / maxLength
```
Added value: +100
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "currency": {
+      "description": "ISO 4217 code every from_price_cents below is quoted in, e.g. \"EUR\".",
+      "type": "string"
+    },
+    "destinations": {
+      "description": "The matching destinations. Empty when nothing matched.",
+      "items": {
+        "properties": {
+          "currency": {
+            "description": "ISO 4217 code the from_price_cents beside it is expressed in, which is the currency you asked for, e.g. \"EUR\". Null exactly when from_price_cents is null, which is what a country nested on a plan answers: nothing priced it there.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "from_price_cents": {
+            "description": "Cheapest plan for this destination, in minor units (cents) of the response currency, so 1250 is 12.50. Null when this response did not price the destination.",
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "iso2": {
+            "description": "ISO 3166-1 alpha-2 code, e.g. \"ES\". This is the code list-plans and plan-trip take.",
+            "type": "string"
+          },
+          "iso3": {
+            "description": "ISO 3166-1 alpha-3 code, e.g. \"ESP\".",
+            "type": "string"
+          },
+          "links": {
+            "properties": {
+              "country": {
+                "properties": {
+                  "path": {
+                    "description": "Path on the storefront, e.g. \"/esim/es\".",
+                    "type": "string"
+                  },
+                  "query": {
+                    "description": "Query parameters that belong on the path, as an object. Empty when there are none.",
+                    "type": "object"
+                  },
+                  "url": {
+                    "description": "The full storefront URL for this country's storefront page. Safe to show to a person.",
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "path",
+                  "query",
+                  "url"
+                ],
+                "type": "object"
+              }
+            },
+            "required": [
+              "country"
+            ],
+            "type": "object"
+          },
+          "name": {
+            "description": "English country name, e.g. \"Spain\".",
+            "type": "string"
+          },
+          "region": {
+            "description": "The region this country is filed under, e.g. \"Europe\". Null when it is filed under none.",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "name",
+          "iso2",
+          "iso3",
+          "region",
+          "from_price_cents",
+          "currency",
+          "links"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "returned": {
+      "description": "How many destinations are in this response.",
+      "type": "integer"
+    },
+    "total": {
+      "description": "How many destinations matched, before `limit` was applied.",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "total",
+    "returned",
+    "currency",
+    "destinations"
+  ],
+  "type": "object"
+}

First observedSep 11, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered; the description still adds that it 'answers from the SimFuse catalog alone,' confirming there is no external lookup, and discloses the currency fallback behaviour. It does not add much beyond annotations and schema on pagination or response shape, keeping it below 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?

Front-loaded with the core purpose and payload in the first sentence, then routing guidance, then the read-only/catalog caveat. Four sentences, none redundant, and the most decision-relevant information comes first.

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?

An output schema exists, so return values need not be described. For a three-optional-parameter, read-only catalog tool, the description covers purpose, payload, routing to siblings, and safety context — nothing an agent needs to call it correctly is missing.

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 per-parameter documentation is already complete and the baseline is 3. The description adds workflow-level meaning: the search parameter is framed as the mechanism that 'turns "Portugal" into the two-letter country code the other tools take,' and currency is tied to the quoting of the 'from' price, which is more than the schema states.

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 states a specific verb and resource (list the countries SimFuse sells eSIMs for), plus the concrete payload (cheapest 'from' price per destination in the requested currency). It explicitly separates itself from list-plans (single destination) and plan-trip (multi-country), so an agent can route without opening a 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?

It gives an explicit trigger ('Start here when someone names a place') and names both alternatives with the conditions that select them: list-plans for one destination, plan-trip for two or more countries. When-to-use, when-to-switch, and alternatives are all present.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?