AeroCell: eSIM Travel Data

Find AeroCell eSIM plans

find_esim_plans

Read-only

Find current AeroCell travel eSIM plans for one country. Use a two-letter ISO country code. Provide both travel dates if known; plans covering the whole trip are returned by default. Optional data and USD price filters narrow results.

Input Schema

Name	Required	Description
`limit`	No	Maximum results, 1–20; default 8.
`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_code`	Yes	Two-letter ISO country code, such as JP; XK is also supported by the catalog.
`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
`country`	Yes
`currency`	Yes
`trip_days`	Yes
`browse_url`	Yes
`updated_at`	Yes
`total_matching`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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

Changed4 schema fields changedOct 24, 2026

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"
-]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"
+]

First observedOct 13, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare read-only, non-destructive, open-world behavior, so the description only needs to add operational context. It does so by disclosing the default filtering behavior ('plans covering the whole trip are returned by default') and how optional filters interact, though it says nothing about result ordering or empty-result behavior.

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 short sentences, front-loaded with the core action and scope, then usage rules, then filter behavior. No filler or repetition.

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 exists, so return values need not be explained, and annotations cover the safety profile. The description is complete for calling the tool correctly; the only gap is the absence of explicit routing guidance among the three sibling search/get tools.

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%, so all seven parameters are already documented. The description restates the country-code format and the date/filter roles, and clarifies that coverage filtering is the default, but adds no syntax or edge-case detail the schema lacks. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource ('Find current AeroCell travel eSIM plans') plus scope ('for one country'), which implicitly separates it from find_regional_esim_plans. It never names the sibling explicitly, so the differentiation is inferred rather than stated.

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 concrete usage instructions: use a two-letter ISO code, supply both travel dates if known, and use filters to narrow. It stops short of explicitly saying when to prefer find_regional_esim_plans or get_esim_plan instead.

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?