Mappit

Find businesses and places

find_places

Read-onlyIdempotent

Find businesses and landmarks near a place in Mappit's directory of 14.9 million OpenStreetMap entries: by name ("Pike Place Market"), by kind ("pharmacy", "hotel", "cafe") or by cuisine ("ramen"). Nearest first, with address, opening hours, website and phone where OpenStreetMap has them. Data © OpenStreetMap contributors.

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": {
      "near": "<near>"
    },
    "name": "find_places"
  }
}

Input Schema

Name	Required	Description
`q`	No	A name, a kind of place or a cuisine ("Starbucks", "pharmacy", "ramen"). Omit to list what is nearest.
`near`	Yes	Where to look: a place name, a landmark ("Pike Place Market"), a place id or "lat,lon".
`limit`	No	How many: default 10, at most 30.
`category`	No	One of: food-drink, shopping, health, services, culture, recreation, education, lodging, office.
`radius_km`	No	How far to look in km: default 5, at most 50.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 20, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the safety profile is covered. The description goes further by disclosing the data source (OpenStreetMap), result ordering ('Nearest first'), and which attributes come back (address, opening hours, website, phone), which an agent cannot infer from annotations alone.

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?

Front-loaded with the core action and scope in a single dense sentence, with examples inline. The trailing attribution ('Data © OpenStreetMap contributors') is licensing boilerplate rather than agent-relevant guidance, costing a small amount of space.

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 no output schema, the description usefully tells the agent what fields to expect back and how results are ordered. Defaults, limits and accepted input forms are handled by the schema, so nothing essential is missing for a 5-parameter read-only search.

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 all five parameters and their defaults/limits are already documented. The description's restatement of q's flexibility (name/kind/cuisine) largely duplicates the schema, adding no syntax or edge-case detail beyond it.

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?

States a specific verb (Find) and resource (businesses and landmarks near a place), plus the underlying corpus (14.9 million OpenStreetMap entries). This is clearly distinguishable from siblings like get_directions, get_location, and search_mappit without opening a schema.

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 when to reach for this tool (proximity search against a POI directory) and shows three query modes (name, kind, cuisine), but it never names an alternative or states when NOT to use it — e.g. versus get_directions for routes or get_location for a single place. Usage is inferable rather than explicit.

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

All Mappit 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?