sinoconnection-esim-mcp

get_plan_details

Read-only

Full details for a specific plan by id — call this WHENEVER the customer selects or shows interest in a plan; do NOT just quote a bare price. Returns coverage, networks, activation window and fair-usage detail PLUS whats_included (concrete selling points: instant QR delivery, keep-your-own-number data-only eSIM, buy-now/travel-later install window, easy Wi-Fi setup, bilingual English/中文 support, and China no-VPN where applicable) and a positive unlimited_note for unlimited plans. Present the 3–5 most relevant selling points together with the price (and any discount) to help the customer decide, THEN confirm eSIM compatibility + carrier-unlock before offering the checkout link. Use before create_checkout_link.

Input Schema

Name	Required	Description	Default
`id`	Yes	Package id from search_esim_plans

Output Schema

Name	Required	Description
`plan`	No
`error`	No
`currency`	No
`coverage_count`	No
`unlimited_note`	No
`whats_included`	No	Fact-based selling points to present to the customer

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 11, 2026

addedOutput schema / properties / plan / properties / networks_in_country

Added value: +{
+  "description": "Networks the recommended plan uses in the searched country",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / plan / properties / recommended

Added value: +{
+  "description": "China searches: true on the regional Asia plans that lead the results",
+  "type": "boolean"
+}

Changed2 schema fields changedJul 16, 2026

addedOutput schema / properties / plan / properties / flag

Added value: +{
+  "description": "Destination flag emoji to lead the plan with",
+  "type": "string"
+}

addedOutput schema / properties / plan / properties / highlight

Added value: +{
+  "description": "Compact one-line value pitch to relay to the customer",
+  "type": "string"
+}

Changed3 schema fields changedJul 16, 2026

addedOutput schema / properties / coverage_count
```
Added value: +{
+  "type": "integer"
+}
```

addedOutput schema / properties / unlimited_note

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / whats_included

Added value: +{
+  "description": "Fact-based selling points to present to the customer",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed1 schema field changedJul 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "currency": {
+      "type": "string"
+    },
+    "error": {
+      "type": "string"
+    },
+    "plan": {
+      "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": "object"
+}

First observedJul 9, 2026

TDQS

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 openWorldHint=true, so safety is covered; the description adds the workflow context that makes those hints actionable (safe to call on every plan view, and the sequence of compatibility/unlock checks before checkout). It spends a lot of text enumerating return fields that the output schema already carries, which dilutes the behavioral value slightly.

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

Conciseness3/5

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

Purpose and the routing rule are correctly front-loaded, but the middle is a dense run-on that embeds an enumerated list of example selling points and a multi-step sales script. Much of that is agent-prompt material rather than tool-selection material, so several clauses fail the 'every sentence earns its place' test.

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?

For a single-id read tool with an output schema, annotations, and full schema coverage, the description covers purpose, invocation trigger, ordering against siblings, and the shape of the returned content. 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter is documented in the schema as 'Package id from search_esim_plans'. The description only restates 'by id', adding no format or sourcing detail beyond the schema, so the baseline 3 applies.

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+resource ('Full details for a specific plan by id') and immediately differentiates itself from siblings by naming search_esim_plans as the id source and create_checkout_link as the downstream step. An agent knows exactly what this returns and where it fits in the flow 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use ('call this WHENEVER the customer selects or shows interest in a plan'), explicit when-not ('do NOT just quote a bare price'), and an explicit ordering constraint ('Use before create_checkout_link'). This is about as unambiguous as routing guidance gets.

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

All sinoconnection-esim-mcp 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.