Skip to main content
Glama
Sign In

mu

by mu.micro
OverviewDiscussionsAdmin

Search places

places_search
Read-onlyIdempotent

Find places by name or category, optionally near a location. Each one says whether it is open right now where that is known, rather than raw opening-hours text to interpret

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": {
      "query": "<query>"
    },
    "name": "places_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoOptional latitude, if the location is already known
lonNoOptional longitude, if the location is already known
nearNoOptional place to search near, e.g. 'Shoreditch, London' or 'SF'
queryYesWhat to look for, e.g. 'ramen', 'pharmacy', 'Blue Bottle Coffee'
radiusNoOptional search radius in metres (default 2000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed7 schema fields changed
    • addedInput schema / properties / lat
      Added value: +{
+  "description": "Optional latitude, if the location is already known",
+  "type": "number"
+}
    • addedInput schema / properties / lon
      Added value: +{
+  "description": "Optional longitude, if the location is already known",
+  "type": "number"
+}
    • changedInput schema / properties / near / description
      Previous value: -"Location name or address to search near"New value: +"Optional place to search near, e.g. 'Shoreditch, London' or 'SF'"
    • removedInput schema / properties / near_lat
      Removed value: -{
-  "description": "Latitude of the search location",
-  "type": "number"
-}
    • removedInput schema / properties / near_lon
      Removed value: -{
-  "description": "Longitude of the search location",
-  "type": "number"
-}
    • changedInput schema / properties / query / description
      Previous value: -"Search query (e.g. cafe, pharmacy, Boots)"New value: +"What to look for, e.g. 'ramen', 'pharmacy', 'Blue Bottle Coffee'"
    • changedInput schema / properties / radius / description
      Previous value: -"Search radius in metres, 100–5000 (default 1000)"New value: +"Optional search radius in metres (default 2000)"
  4. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only and idempotent behavior, so the description adds useful context by explaining that results indicate whether each place is currently open 'where known' rather than returning raw opening-hours text. This is meaningful behavioral information beyond the structured annotations.

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?

The description is short, front-loaded, and every sentence earns its place. The primary purpose comes first, and the second sentence adds valuable behavioral context without redundancy.

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?

Given the 100% schema description coverage, the read-only annotations, and the tool's simple query-focused nature, the description provides enough context to invoke the tool correctly. It lacks an explicit comparison to places_nearby and does not describe the full return shape, but neither is necessary for basic correct invocation.

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 are already documented. The description only restates the 'optionally near a location' idea without adding deeper parameter semantics, so it neither significantly helps nor harms parameter understanding.

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 clearly states what the tool does: find places by name or category, optionally near a location. It provides a specific verb and resource, and the open-status clarification helps set expectations, though it does not explicitly differentiate from sibling tools like places_nearby.

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 by mentioning searching by name or category with an optional location, but it does not explicitly say when to prefer this over related tools such as places_nearby or places_geocode. No alternatives or exclusions are named, leaving the differentiation to inference.

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

All mu toolsInspect
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