Skip to main content
Glama
Sign In
chinastay-travel-mcp

chinastay-travel-mcp

by MileyFu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Check China Visa & 240h Transit Eligibility

check_china_visa_transit
Read-onlyIdempotent

Verify 2026 China visa and 240-hour Transit Without Visa eligibility from passport country, origin, onward destination, entry port, and stay length to prevent boarding denials.

Instructions

Authoritative 2026 China visa & 240-Hour (10-Day) Transit Without Visa (TWOV) compliance checker. Call this BEFORE answering any China entry, layover, or visa-exemption question to avoid outdated 144-hour info or round-trip boarding denials (Country A -> China -> Country C rule across 57 TWOV nations & 65+ open ports). Returns exact eligibility verdict, permitted travel area, refusal risks, and verified https://chinastay.org/visa-free// deep links.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "passport_country": "<passport_country>"
    },
    "name": "check_china_visa_transit"
  }
}

Input Schema

NameRequiredDescriptionDefault
purposeNoPrimary visit purpose (defaults to "tourism"). Employment, full-time study, and journalism always require Z/X/J visas.
entry_portNoChinese entry airport/port code or city (e.g. "PVG", "PEK", "PKX", "SZX", "CAN", "CTU", "Shanghai", "Shenzhen"). Defaults to PVG (Shanghai Pudong).
onward_countryNoConfirmed THIRD destination country/territory AFTER Mainland China (Country C, e.g. "Hong Kong", "Japan", "South Korea", "Singapore"). Note: Hong Kong, Macau, and Taiwan qualify as Country C, whereas returning to Country A violates TWOV.
origin_countryNoCountry or overseas territory you fly FROM into Mainland China (Country A, e.g. "United States", "Japan", "Hong Kong"). Required for TWOV-only passports such as US or UK.
passport_countryYesPassport country name or ISO-2 code (e.g. "United States", "US", "UK", "France", "Germany", "Australia", "Japan", "Brazil").
planned_stay_hoursNoPlanned stay duration in hours (defaults to 240). 240h TWOV max is 240 hours (10 days).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds useful scope context — the Country A -> China -> Country C rule, 57 TWOV nations, 65+ open ports — but does not disclose what happens when optional inputs are omitted or how verdicts degrade with partial data.

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?

Three sentences, front-loaded with the purpose and then the call trigger, with the return payload last. Slightly promotional framing ('Authoritative', 'verified') costs a little, but every sentence carries routing or output information.

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 read-only lookup with no output schema, the description adequately reports what comes back: eligibility verdict, permitted travel area, refusal risks, and deep links. The remaining gap is behavioral edge cases — how it responds to a missing origin_country for non-TWOV passports or an out-of-range stay duration.

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 coverage is 100%, so the baseline is 3. The description still earns credit above baseline by spelling out the Country A (origin) -> China -> Country C (onward) relationship that makes origin_country and onward_country meaningful together, which the schema's individual field descriptions only imply.

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 names a specific verb and resource — a 2026 China visa / 240-hour TWOV compliance checker — and scopes it to entry, layover, and visa-exemption questions. It is unmistakably distinct from the sibling tools (app status, FX rates, driver cards), so an agent can select it 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 Guidelines4/5

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

It gives an explicit trigger: call this BEFORE answering any China entry, layover, or visa-exemption question, and names the failure mode it prevents (outdated 144-hour info, round-trip boarding denials). No explicit when-not condition or named alternative is given, but the applicable domain is clear enough to route correctly.

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

Deploy Server

Other Tools