Shanghai Streets Travel Guide

Find Nearby Places, Routes and Areas

find_nearby

Read-onlyIdempotent

Group itinerary stops geographically or find nearby restaurants, sights, walking routes and areas around a coordinate (lat, lon) or an existing place (place_id), sorted by distance_km.

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

Input Schema

Name	Required	Description
`lat`	No	Center latitude (required unless place_id is provided).
`lon`	No	Center longitude (required unless place_id is provided).
`limit`	No	Maximum results to return (default 20, max 100).
`family`	No	Optional broad family filter (e.g. food, sights, drinks).
`category`	No	Optional specific category key filter.
`place_id`	No	Existing place ID or slug to search around instead of lat/lon.
`radius_km`	No	Search radius in kilometers (default 2, max 50).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one useful behavioral fact beyond the schema: results are sorted by distance_km. It says nothing about result shape, pagination, or what happens when radius_km excludes everything, so the added behavioral value is modest.

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 well-formed sentence with the primary search behavior front-loaded and no filler. It loses a point because the leading 'Group itinerary stops geographically' clause is unsupported by any parameter and forces the reader to reconcile two unrelated modes.

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?

The schema is complete with defaults and ranges and no output schema exists, so the description only needs to orient the agent, which it largely does. The only real gap is the dangling 'group itinerary stops' capability, which has no corresponding input and could mislead an agent trying to use this tool for itinerary grouping.

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 lat, lon, place_id, radius_km, family, category and limit are all already documented with ranges and defaults. The description only restates lat/lon and place_id as alternative center points and mentions distance_km ordering; it adds no filtering syntax or interplay guidance (e.g. family vs category) beyond the schema.

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 ('find') and resource ('nearby restaurants, sights, walking routes and areas') with the two locating modes (coordinate or place_id) spelled out. It is distinguishable from get_place/get_area by being a proximity search. The opening clause 'Group itinerary stops geographically' is a second, unrelated capability that no parameter supports, which blurs rather than sharpens the purpose.

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?

The description implies usage ('find nearby ... around a coordinate or an existing place') but never states when to pick this over search_places or the get_* lookups, nor does it say when the lat/lon mode should be used instead of place_id. Usage is inferable from the parameter semantics but not explicitly guided.

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?