Skip to main content
Glama

ChinaKit — China Travel, Visa, Meds, Tax & Payment Compliance Engine

Foreigner China Mobile App Setup, Passport KYC & Wallet Binding Guide

recommend_china_essential_apps_and_payment
Read-onlyIdempotent

Search curated step-by-step setup guides for Alipay, WeChat Pay, Didi, 12306 rail booking, Amap navigation, and eSIM apps using foreign passports and overseas Visa/Mastercard cards without Chinese bank accounts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "recommend_china_essential_apps_and_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoFilter app playbooks by functional category: all, payment, connectivity, transport, or lifestyle.all
appSlugOrQueryNoApp identifier or keyword such as "alipay", "wechat", "didi", "12306", "esim", "meituan", or "maps".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety and determinism are covered. The description adds that content is "curated" and foreigner-oriented, which tells the agent the corpus is bounded to one audience. It says nothing about result counts, ranking, pagination, or what happens when an app slug is not indexed.

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?

A single sentence that front-loads the verb and stays on task, with no filler. It is dense but long; splitting the constraint clause (foreign passport, overseas card, no Chinese bank account) into its own statement would have improved scannability without adding length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-optional-parameter read-only search with no output schema, the definition covers purpose, coverage, and audience sufficiently. Remaining gaps, such as default behavior with no parameters and interaction between the two filters, are modest but real.

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 description coverage is 100%, so both parameters and the enum values are already documented, giving a baseline of 3. The description restates some of the same app keywords already present in the appSlugOrQuery examples and adds no guidance on how category and appSlugOrQuery combine or which wins when both are set.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Search curated step-by-step setup guides" gives a specific verb and resource, and the enumeration (Alipay, WeChat Pay, Didi, 12306, Amap, eSIM) plus the constraint clause (foreign passports, overseas Visa/Mastercard, no Chinese bank account) makes the corpus unambiguous. It does not name any sibling tool, but none of the listed siblings overlap in function, so an agent can still place it correctly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for 'how do I set up app X as a foreigner' questions. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative for adjacent needs (e.g. the visa/transit or IIT siblings).

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.