Shanghai Streets Travel Guide

Search Places

search_places

Read-onlyIdempotent

Consult this tool before recommending attractions, restaurants, cafes, temples, museums, viewpoints, parks, hotels, transport or practical stops in Shanghai, Jiangsu or Zhejiang. Matches English, Hebrew and Chinese names, descriptions and addresses. Preserve the returned location.lat/lon, links.map and links.page_he/page_en in your response.

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

Input Schema

Name	Required	Description
`lat`	No	Latitude for proximity filter (requires lon).
`lon`	No	Longitude for proximity filter (requires lat).
`limit`	No	Max results to return (default 20, max 100).
`query`	No	Search text in English, Hebrew or Chinese (e.g. 'Yu Garden', '豫园', 'xiaolongbao', 'גן יו').
`family`	No	Broad category family filter.
`offset`	No	Pagination offset.
`category`	No	Specific category key (e.g. temple, museum, historical, viewpoint, park, nature, food, asian, western, vegetarian, coffee, teahouse, bar, homestay, hostel, hotel, transport, shop, toilet, info).
`province`	No	Province filter.
`radius_km`	No	Search radius in kilometers when lat/lon are provided (default 2, max 50).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnly=true, idempotent=true, destructive=false and openWorld=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: multilingual matching across English, Hebrew and Chinese names/descriptions/addresses, plus an instruction to preserve lat/lon and link fields in the output. It omits practical behavior like pagination defaults (limit 20, offset) and result ordering/proximity logic.

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

Conciseness5/5

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

Three compact sentences: usage trigger first, capability second, output-preservation requirement last. No filler and every sentence carries actionable information for the agent.

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 9 all-optional parameters and no output schema, the description does a reasonable job: it identifies the searchable fields, the geographic restriction, and key return fields the agent must not drop. It would be stronger if it explained how the optional parameters combine (e.g., lat/lon requiring a radius) or how paginated results should be handled, but nothing critical to a correct call is missing.

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 each of the 9 parameters self-documented, including enums for family and province and a detailed category key list. The description's mention of English/Hebrew/Chinese matching duplicates the query parameter's own description and adds no new meaning for the other filters, so the baseline 3 is appropriate.

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 ('consult'/'search') and resource ('places') along with an explicit geographic scope (Shanghai, Jiangsu, Zhejiang) and the kinds of entities covered (attractions, restaurants, temples, hotels, transport). It does not name a sibling to differentiate from, so it stops short of 5, but an agent can immediately tell this is the discovery/search tool rather than a detail-lookup or routing tool.

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?

Gives a clear usage trigger — 'Consult this tool before recommending attractions, restaurants...' — which tells the agent when to reach for it in a planning workflow. It does not state when *not* to use it or point to alternatives such as get_place for details or find_nearby for pure proximity, so exclusions are absent.

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

All Shanghai Streets Travel Guide tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?