Skip to main content
Glama

Get China Viral Spot Coordinates & Taxi Driver Flashcards

get_viral_spot_driver_card
Read-onlyIdempotent

Get verified ground coordinates, Chinese taxi/DiDi driver flashcards, and mistake warnings for viral China landmarks so drivers find the exact spot without GPS shift errors.

Instructions

Verified ground coordinates (with Apple Maps links free of Google Maps' ~500m China GPS shift), Chinese taxi/DiDi driver flashcards, driver avoid-mistake warnings, and passport/payment workarounds for China's most viral landmarks (e.g. Shenzhen Meituan drone coffee delivery, Wuhan Apollo Go robotaxi, Chongqing Hongyadong / Kuixinglou 8D cliff, Liziba monorail). Always call this instead of inventing Chinese street addresses.

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_viral_spot_driver_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoOptional city name filter (e.g. "Shenzhen", "Wuhan", "Chongqing", "Chengdu", "Shanghai", "Beijing").
queryNoLandmark, creator moment, or keyword (e.g. "drone", "robotaxi", "chongqing", "hongya", "monorail", "pandabase"). Omit to return all viral spots (optionally filtered by city).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish this as a read-only, idempotent, non-destructive, closed-world lookup, so the description's job is lighter. It still adds real value by disclosing that coordinates are verified and Apple Maps links avoid the ~500m China GPS offset, and that results bundle driver flashcards and avoid-mistake warnings — context an agent could not infer from the schema.

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

Conciseness3/5

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

The content is front-loaded with the useful scope and the mandatory-use rule, but the single sentence is overloaded with marketing-style parentheticals and a long list of landmark examples that partly duplicate the query parameter's examples. It is readable but not tight.

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 filter parameters, full schema coverage, and no output schema, the description covers what the tool returns and when to use it. What is missing — the shape of the returned record and whether results are exhaustive — is minor given the tool's simplicity.

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 the city and query parameters are already fully documented with examples. The description adds no parameter-level meaning beyond the schema, which is acceptable given the schema's completeness and yields the baseline score.

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?

The description names a specific resource (verified ground coordinates, driver flashcards, warnings, and payment/passport workarounds for viral China landmarks) and illustrates it with concrete examples like Meituan drone coffee and Apollo Go robotaxi. It is clearly distinct from the sibling tools (rates, app status, visa transit), though it never names those siblings to make the differentiation explicit.

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 one explicit directive: always call this rather than inventing Chinese street addresses, which tells the agent when the tool is mandatory. There are no stated exclusions or named alternative tools, so the guidance is clear but one-sided.

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