AeroCell: eSIM Travel Data

Find AeroCell regional eSIM plans

find_regional_esim_plans

Read-only

Find live multi-country AeroCell bundles. Supply every itinerary country as a two-letter ISO code; only bundles listing all those countries are returned. Optionally select a named region. A region-only search returns bundles with their exact country coverage.

Input Schema

Name	Required	Description
`limit`	No	Maximum results, 1–20; default 8.
`region`	No	Optional named catalog region; check returned country_codes.
`end_date`	No	Trip end, YYYY-MM-DD inclusive. Provide with start_date.
`start_date`	No	Trip start, YYYY-MM-DD. Provide with end_date.
`min_data_gb`	No	Minimum data allowance in GB.
`country_codes`	No	Every itinerary country, up to 30 distinct codes.
`max_price_usd`	No	Maximum price in USD.
`require_trip_coverage`	No	Defaults to true when dates are supplied; false includes shorter plans.

Output Schema

Name	Required	Description	Default
`note`	Yes
`plans`	Yes
`region`	Yes
`currency`	Yes
`trip_days`	Yes
`browse_url`	Yes
`updated_at`	Yes
`total_matching`	Yes
`requested_country_codes`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 24, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```

Changed5 schema fields changedOct 24, 2026

changedInput schema / properties / region / enum

Previous value: -[
-  "global",
-  "europe",
-  "asia_pacific",
-  "southeast_asia",
-  "latin_america",
-  "middle_east_north_africa",
-  "gulf"
-]New value: +[
+  "global",
+  "europe",
+  "north_america",
+  "asia_pacific",
+  "southeast_asia",
+  "latin_america",
+  "middle_east_north_africa",
+  "gulf"
+]

addedOutput schema / properties / plans / items / properties / includes_calls
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / plans / items / properties / includes_sms
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / plans / items / properties / provider_details

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "content": {
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "title",
+      "content"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / properties / plans / items / required

Previous value: -[
-  "id",
-  "name",
-  "data_gb",
-  "validity_days",
-  "price_usd",
-  "network",
-  "operators",
-  "covers_trip",
-  "plan_page_url",
-  "checkout_url",
-  "region_code",
-  "country_codes",
-  "country_count"
-]New value: +[
+  "id",
+  "name",
+  "data_gb",
+  "validity_days",
+  "price_usd",
+  "network",
+  "operators",
+  "covers_trip",
+  "includes_calls",
+  "includes_sms",
+  "provider_details",
+  "plan_page_url",
+  "checkout_url",
+  "region_code",
+  "country_codes",
+  "country_count"
+]

First observedOct 13, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, openWorld and non-destructive, so the description is free to add real semantics — the AND-match rule across country_codes, the fact that a region-only search returns exact country coverage, and that results are "live" bundles. It adds no auth, rate-limit, or pagination context, which is the remaining gap.

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?

Three tightly written sentences, front-loaded with the verb and resource, then the required input rule, then the optional mode. No repetition of schema or annotation content.

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?

An output schema, full annotation coverage and 100% schema descriptions carry most of the load, and the description covers the non-obvious matching logic. The interaction between country_codes and region when both are provided is the one behavioral detail an agent must still guess at.

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 3 is the baseline; the description earns above that by explaining the conjunctive matching semantics of country_codes and the returned coverage for region-only queries. It does not clarify what happens when both country_codes and region are supplied (narrow vs. override), which is the one semantic still ambiguous.

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?

States a specific verb and resource ("Find live multi-country AeroCell bundles") and the multi-country qualifier immediately separates it from find_esim_plans and get_esim_plan. An agent can tell what this tool retrieves without opening the schema.

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?

Gives explicit operating instructions: pass every itinerary country as ISO codes, and bundles must list all of them to be returned; a region-only search is also described as a valid mode. It never names find_esim_plans or states when to prefer that sibling, so the routing rule is clear but not exhaustive.

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

All AeroCell: eSIM Travel Data 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?