Skip to main content
Glama

sinoconnection-esim-mcp

search_esim_plans

Read-only

Search travel eSIM plans for any of 200+ countries. Specialized China plans deliver uncensored internet WITHOUT a VPN (unlike most eSIMs, which are throttled or blocked in China) β€” only when the plan's china_open_internet field is true. Also covers regional Asia and worldwide bundles. Quote price_usd β€” that is the price the customer pays in USD, with any current sitewide discount already applied; list_price_usd is the original and on_sale/discount_pct show the saving. If is_fair_usage_policy is true, the plan is NOT truly unlimited β€” relay the cap. PRESENT RESULTS ATTRACTIVELY TO BOOST SALES: lead each plan with its flag emoji + the title, put the price in bold, strike or note the discount when on_sale, and show the highlight value line (it already includes πŸ”“/🌍/πŸ“±/⚑/πŸ’° icons). Lay plans out as a clean, scannable list or a markdown table with a flag column; recommend a best-value pick. Call get_plan_details for the full pitch once the customer shows interest.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNo
regionNoRegion slug: asia | europe | mea | namerica | latam | oceania
countryNoISO-2 country code, e.g. CN, JP, KR
durationNoExact validity in days (optional filter)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
plansNo
totalNo
currencyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / plans / items / properties / flag
      Added value: +{
      +  "description": "Destination flag emoji to lead the plan with",
      +  "type": "string"
      +}
    • addedOutput schema / properties / plans / items / properties / highlight
      Added value: +{
      +  "description": "Compact one-line value pitch to relay to the customer",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "currency": {
      +      "type": "string"
      +    },
      +    "plans": {
      +      "items": {
      +        "properties": {
      +          "activation_policy": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "china_open_internet": {
      +            "description": "Open/uncensored internet in China without a VPN",
      +            "type": "boolean"
      +          },
      +          "coverage_codes": {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "data_amount": {
      +            "type": "string"
      +          },
      +          "discount_pct": {
      +            "type": "number"
      +          },
      +          "fair_usage_policy": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "id": {
      +            "type": "string"
      +          },
      +          "install_window_days": {
      +            "type": [
      +              "integer",
      +              "null"
      +            ]
      +          },
      +          "is_fair_usage_policy": {
      +            "type": "boolean"
      +          },
      +          "is_unlimited": {
      +            "type": "boolean"
      +          },
      +          "list_price_usd": {
      +            "description": "Original price before discount",
      +            "type": "number"
      +          },
      +          "networks": {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "on_sale": {
      +            "type": "boolean"
      +          },
      +          "price_usd": {
      +            "description": "Price the customer pays (current discount applied)",
      +            "type": "number"
      +          },
      +          "title": {
      +            "type": "string"
      +          },
      +          "validity_days": {
      +            "type": "integer"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "total": {
      +      "type": "integer"
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, which the description does not contradict. The description adds value by explaining pricing fields (price_usd is final), fair usage policy flag, and instructions to present results attractively, going beyond what annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is relatively long but each sentence serves a purpose. It front-loads the main purpose and then provides important details about pricing and presentation. Could be slightly more concise but not wasteful.

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?

Given the parameter count, schema coverage, output schema existence, and rich annotations, the description provides sufficient additional context about pricing, fair usage, presentation, and integration with get_plan_details. It feels complete for an AI agent to use correctly.

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 75% and description adds some context (e.g., ISO-2 country codes, region slugs), but much is already in the schema. The description provides additional context about China plans but does not significantly enhance parameter understanding beyond the schema.

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 clearly states it searches travel eSIM plans for 200+ countries, with specialized China plans and regional/worldwide bundles. It distinguishes itself from siblings by mentioning get_plan_details for full pitch and implying check_device_compatibility and create_checkout_link are separate tools.

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 explains when to use this tool (to search plans) and when to call get_plan_details (after customer interest). It does not explicitly state when not to use it, but the context is clear and it mentions alternatives implicitly.

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.