Skip to main content
Glama

Get China City Fixer, Bilingual Interpreter & Tour Guide Dossiers

get_city_fixer_rates
Read-onlyIdempotent

Retrieves verified bilingual fixer, interpreter, medical/business escort, sourcing, and zero-commission guide rates for major China cities, including tiered pricing, scenarios, and booking links.

Instructions

Retrieves ChinaStay verified private bilingual (C2 English) interpreter, medical/business escort, hardware sourcing fixer, and zero-commission tour guide dossiers across major China hubs (Beijing, Shanghai, Xi’an, Jiujiang/Lushan, Guangzhou, Chengdu, Shenzhen), including progressive rate tiers, scenarios, insider rules, $69 Pre-Flight Route Audit info, and direct booking links.

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": "get_city_fixer_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity slug or name: "beijing", "shanghai", "xian" (or "Xi'an"), "jiujiang", "guangzhou", "chengdu", or "shenzhen". Omit to compare all 7 supported cities.
include_faqsNoWhether to include city-specific fixer FAQs in detailed dossier responses (defaults to true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

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 the safety profile is covered. The description adds useful content context beyond that: dossiers include progressive rate tiers, scenarios, insider rules, audit info, and booking links, which tells the agent what to expect in the payload. It does not discuss authentication, rate limits, or response size when comparing all seven cities, leaving gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single very long sentence that front-loads the verb but then piles on promotional modifiers ('C2 English', 'zero-commission', '$69 Pre-Flight Route Audit info') that do not help an agent select or invoke the tool. Marketing copy crowds out actionable guidance, so it is bloated rather than efficiently concise.

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?

With only two optional parameters and no output schema, the description usefully enumerates what the dossiers contain (rate tiers, scenarios, insider rules, booking links), compensating for the absent return-value documentation. What remains missing is how the multi-city comparison behaves when city is omitted and roughly how large such a response is.

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%, with both the city slug list and the include_faqs default fully documented in the schema, so the baseline is 3. The description reinforces that results span seven major hubs but adds no format, alias, or behavior detail beyond the schema for either parameter.

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 opens with a specific verb and resource: 'Retrieves ChinaStay verified ... dossiers,' and enumerates the exact provider types (bilingual interpreter, medical/business escort, hardware sourcing fixer, zero-commission tour guide) and the covered hubs. That is clearly distinguishable from siblings like get_viral_spot_driver_card or check_china_visa_transit, which cover unrelated resources.

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 content: an agent can infer it is for sourcing vetted local fixers/guides in Chinese cities. There is no explicit when-to-use, when-not-to-use, or named alternative for related needs (e.g., visa or app-status queries handled by siblings). The only directive-like sentence concerns omitting the city parameter, which is parameter guidance rather than usage guidance.

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