sinoconnection-esim-mcp

check_device_compatibility

Read-only

Check whether a phone/tablet model supports eSIM before recommending a plan. Free-text device name in; compatible yes/no plus closest matches out. IMPORTANT: eSIM hardware support is only HALF the requirement — the phone must ALSO be carrier-unlocked. This tool returns an unlock_required flag + how to verify; always relay it, because a locked phone cannot use a travel eSIM.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`device`	Yes	e.g. "iPhone 14 Pro", "Galaxy S24"

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	No
`matched`	No
`candidates`	No
`compatible`	No
`unlock_note`	No
`unlock_required`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "candidates": {
+      "type": "array"
+    },
+    "compatible": {
+      "type": "boolean"
+    },
+    "matched": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "note": {
+      "type": "string"
+    },
+    "unlock_note": {
+      "type": "string"
+    },
+    "unlock_required": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

First observedJul 9, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations (readOnlyHint, openWorldHint) are supplemented with critical behavior: unlock flag, instruction to relay it, and that eSIM support alone is insufficient. No contradiction.

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 sentences, purpose first, no wasted words. Important warnings are highlighted with 'IMPORTANT:' and '+'. Front-loaded and scannable.

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 output schema exists, description covers key outputs (compatible yes/no, closest matches, unlock_required flag). Complete for decision-making without over-explaining.

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?

Schema covers parameter with example values, description adds 'Free-text device name in' clarifying input flexibility. With 100% coverage, description complements schema well.

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 the tool checks eSIM support for a device, with specific use case 'before recommending a plan'. It distinguishes from siblings like search_esim_plans by focusing on hardware compatibility.

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?

Explicitly advises using 'before recommending a plan' and highlights the unlock requirement. While not listing when not to use, the context is clear and siblings are provided for reference.

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.