A
license-
qualityC
maintenanceBrowse, compare, and purchase eSIMs for 190+ countries via AI agents. 12 tools for searching 2,300+ data plans, checking coverage, and buying eSIMs with crypto or card. No account required for browsing.
MIT
eSIM Eagle Plan Finder
Server Details
Find public eSIM plans by destination, trip length, data needs, currency, and locale.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.4/5.0
Tool DescriptionsA
Average 4.3/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
With only one tool, there is no possibility of confusion or overlap. The tool's purpose is clearly defined for finding eSIM plans.
Naming Consistency5/5
The single tool name follows a clean verb_noun pattern (find_esim_plans), and there are no conflicting naming conventions.
Tool Count4/5
The server contains exactly one tool that fulfills its stated purpose as a plan finder. While this is on the low end of typical tool counts, it is well-scoped for a focused lookup service.
Completeness5/5
The tool accepts all relevant parameters and returns actionable results with a checkout URL, covering the complete finder workflow without dead ends.
Available Tools
1 toolfind_esim_plansFind Esim Plans ToolARead-onlyInspect
Finds up to five live eSIM plans that cover every requested country or region, priced for the trip length, data need, currency, and locale. Use the returned checkout URL to buy.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| locale | No | Language for destination names, activation guidance, and checkout URLs. | en |
| currency | No | ISO 4217 display currency code. | USD |
| data_need | No | Expected data usage. Recommended assumes about 500 MB per day. | recommended |
| trip_days | Yes | Number of travel days. | |
| destinations | Yes | One to ten ISO country codes, destination slugs, or exact English destination names, such as JP, japan, or Europe. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| plans | Yes | |
| locale | Yes | |
| message | Yes | |
| currency | Yes | |
| data_need | Yes | |
| trip_days | Yes | |
| plan_count | Yes | |
| destinations | Yes | |
| recommended_data_mb | Yes |
Tool Definition Quality
A4.3/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only safety profile is known. The description adds behavioral context beyond annotations: it returns live plans (not cached), filters to those covering every requested destination, considers pricing factors, and provides a checkout URL for purchase. This adds meaningful behavior without contradicting the annotations.
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?
Two sentences deliver all essential information: the core action and the follow-up. The main verb and resource are front-loaded, and every phrase adds value. No filler or redundant repetition of schema data.
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?
With an output schema present, the description need not enumerate return fields. It sufficiently covers the tool's purpose, constraints ('up to five', 'cover every requested country'), the key input dimensions, and the practical next step ('Use the returned checkout URL to buy'). This is complete for a tool of moderate complexity with no siblings.
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 five parameters are documented. The description reinforces the relevance of trip length, data need, currency, and locale, but does not add new details beyond what the schema already provides. This matches the baseline expectation for high schema coverage.
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 opens with a specific verb ('Finds') and resource ('live eSIM plans'), quantifies the result ('up to five'), and defines scope ('cover every requested country or region'). It clearly distinguishes this from a generic plan search by emphasizing the live and multi-destination coverage aspects.
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?
The description conveys when to use the tool: when you need eSIM plans for specific destinations and a trip duration. The phrase 'priced for the trip length, data need, currency, and locale' implies criteria for selection, and the final sentence gives the next step. No exclusions or alternatives are stated, but sibling tools are absent, so the lack of contrast is acceptable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityBmaintenanceSearch and buy travel eSIMs for 200+ countries, with specialized China plans that deliver uncensored internet without a VPN. Exposes five read-only tools to search plans, check device eSIM compatibility, get plan details, get help, and generate a secure on-site checkout link.MIT
- -license-qualityBmaintenanceLets AI agents search and buy travel eSIMs from ALT eSIM for 200+ destinations, with Stripe payment links and email delivery of QR codes.
- AlicenseAqualityCmaintenanceTravel eSIMs for 193 countries. Stripe + Bitcoin checkout. QR by email in 30s. No API key.4108MIT