Skip to main content
Glama

find_nearby_places

Read-only

Find nearby places by optional category within radius_m.

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": {
      "location": "<location>"
    },
    "name": "find_nearby_places"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNo
locationYes
radius_mNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: no data source, no result cap or ranking order, no pagination, and no note that results depend on an external open-world lookup.

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?

It is a single front-loaded sentence with no wasted clauses, which is good structurally. But the brevity tips into under-specification: the one sentence is doing too little rather than being lean.

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?

Considering the tool's modest complexity (3 params, 1 required), the presence of an output schema removes any need to describe return values, and the annotations cover safety and open-world behavior. The remaining gap is the undocumented nested location object, but the description is adequate for the tool's overall complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it only restates that category is optional and radius is measured in meters. The required 'location' parameter is a free-form object (additionalProperties: true) with no fields documented anywhere, leaving the agent to guess whether it takes lat/lng, an address, or a geocode result.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource combination ('Find nearby places') and names two filtering dimensions (category, radius_m), so the general intent is graspable. However, 'places' is undefined (points of interest? businesses? emergency facilities?) and nothing distinguishes it from adjacent tools like get_emergency_facilities or geocode.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no when-not-to-use, and no mention of alternatives such as geocode, reverse_geocode, or get_emergency_facilities. The agent is left to infer entirely from the name whether this is the right lookup tool for a given question.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.