sinoconnection-esim-mcp

create_checkout_link

Read-only

Create a secure checkout link for a chosen plan (by id). Before sharing the link, confirm with the customer that their phone is (1) eSIM-compatible AND (2) carrier-unlocked — a locked phone cannot use a travel eSIM. The customer completes payment themselves on SinoConnection's checkout page (sign-in required) — you never handle card details. Returns a URL, the plan title, and price_usd (current discount already applied).

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	No
`plan`	No
`error`	No
`checkout_url`	No
`before_you_buy`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "before_you_buy": {
+      "type": "string"
+    },
+    "checkout_url": {
+      "type": "string"
+    },
+    "error": {
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "plan": {
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedJul 9, 2026

TDQS

A3.9/5.0

Behavior1/5

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

The description says 'Create a secure checkout link', implying a write operation, but annotations set readOnlyHint: true, indicating no side effects. This is a direct contradiction. The description adds useful context (payment delegation, prerequisites) but the contradiction undermines transparency entirely.

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?

The description is concise (4 sentences), front-loaded with the main action, and provides additional guidance and return value details without redundancy. Every sentence adds value.

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?

Despite the contradiction, the description covers the tool's purpose, parameter source, essential prerequisites, payment flow, and return values. It is complete for an agent to use correctly, given the simple parameter and output schema.

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?

The parameter 'id' is fully described in the schema (100% coverage). The description adds context by specifying it is a 'Package id from search_esim_plans', which is not in the schema. This helps the agent understand the parameter's source and meaning.

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 'Create a secure checkout link for a chosen plan (by id)', which specifies the action (create), resource (checkout link), and input (plan id). It distinguishes itself from sibling tools like search_esim_plans and check_device_compatibility, which serve different purposes.

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 provides explicit guidance: confirm eSIM compatibility and carrier-unlock before sharing the link. It also explains the payment flow (customer pays on checkout page, agent never handles cards). However, it does not explicitly state when to use this tool versus alternatives, though the context makes it clear it follows plan selection.

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.