Skip to main content
Glama

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

Chinese City & Attraction Passport Ticketing, Transit Zone & Card Readiness Index

lookup_china_destination_foreigner_guide
Read-onlyIdempotent

Query verified attraction entry requirements across China cities (Beijing, Shanghai, Chengdu, Macau, etc.), returning turnstile passport scanning rules, foreign card acceptance, subway exits, and 144/240h transit compatibility.

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": {
      "cityOrAttraction": "<cityOrAttraction>"
    },
    "name": "lookup_china_destination_foreigner_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum matching destination records to return (between 1 and 10).
cityOrAttractionYesChinese city, SAR, province, or landmark name/slug (e.g. "Beijing", "Shanghai", "798 Art Zone", "Macau", "Chengdu").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 the safety profile is covered. The description adds value by naming the specific data classes returned (turnstile scanning, card acceptance, subway exits, transit-window compatibility) and asserting the data is "verified", but it says nothing about coverage gaps, data freshness, or behavior when a destination has no record.

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 front-loaded sentence that puts the resource and the returned data classes first, with no filler or repetition of the title. It is dense but every clause (cities, entry rules, card acceptance, transit compatibility) carries distinct information.

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

Completeness3/5

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

With no output schema, the description must convey return shape, and it does so at a field-class level, which is reasonably adequate for a simple two-parameter lookup. However, it leaves open what a record actually contains structurally, how matches are ranked, and how transit-window compatibility differs from the dedicated transit-visa sibling tool.

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 cityOrAttraction and limit are already documented with examples and bounds. The description adds no further parameter meaning – it does not clarify slug-vs-display-name resolution or how limit interacts with multi-city queries. Baseline 3 applies when the schema carries the parameter burden.

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?

States a specific verb and resource ("Query verified attraction entry requirements across China cities") and enumerates the concrete outputs: turnstile passport scanning rules, foreign card acceptance, subway exits, and 144/240h transit compatibility. It is clear what the tool returns, though it never distinguishes itself from the sibling validate_china_transit_and_visa_free_entry, which appears to cover overlapping transit-visa territory.

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 by the phrasing "Query verified attraction entry requirements" – the agent can infer this is for checking attraction-level entry/ticketing readiness. There is no explicit when-to-use framing, no statement of when to prefer the transit/visa validation sibling instead, and no prerequisites or exclusions.

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.