sinoconnection-esim-mcp

get_help

Read-only

Answer customer support and policy questions about SinoConnection eSIMs: the REFUND POLICY, how to INSTALL (with step-by-step videos), activation, HOW THE NO-VPN CHINA ACCESS WORKS (roaming / exit IP — see faq.how_no_vpn_works), and how to get support. Call this whenever the customer asks about refunds, cancellations, installation/setup, activation, how it works, what IP / does it bypass the firewall, or help — do NOT answer these from memory (especially the IP/firewall question); relay this authoritative content verbatim in meaning.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`faq`	No
`links`	No
`install`	No
`support`	No
`refund_policy`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "faq": {
+      "type": "object"
+    },
+    "install": {
+      "type": "object"
+    },
+    "links": {
+      "type": "object"
+    },
+    "refund_policy": {
+      "type": "object"
+    },
+    "support": {
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

AddedJul 9, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already provide readOnlyHint=true and openWorldHint=true. The description adds context that the tool relays authoritative content verbatim and references a FAQ source (faq.how_no_vpn_works), explaining that answers should not be generated from memory. This goes beyond the annotations without contradicting them.

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 a single paragraph that front-loads the core purpose ('Answer customer support and policy questions about SinoConnection eSIMs') and then lists specific topics. It is dense but each sentence adds value; a minor improvement could be to break into shorter sentences for readability.

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 tool has no parameters and an output schema exists (though not shown), the description fully covers the tool's domain: it enumerates all relevant question types, provides usage context, and references a FAQ. No additional information is needed for an AI agent to correctly invoke it.

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 input schema has zero parameters, and schema description coverage is 100%. Per guidelines, baseline is 4. The description does not need to add parameter meaning, but it effectively explains what the tool does without any parameter overhead.

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 begins with 'Answer customer support and policy questions about SinoConnection eSIMs' and lists specific topics (refund policy, installation, activation, no-VPN access), clearly stating the verb 'answer' and the resource 'customer support and policy questions'. It distinguishes from sibling tools like check_device_compatibility and get_plan_details by focusing on help and policies.

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?

The description explicitly states 'Call this whenever the customer asks about refunds, cancellations, installation/setup, activation, how it works, what IP / does it bypass the firewall, or help' and instructs 'do NOT answer these from memory', providing clear when-to-use and when-not-to-use guidance.

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.