Skip to main content
Glama

search_nearby_poi

Read-onlyIdempotent

Search for geographical Points of Interest (POIs) within a radius (in meters) around a center point specified by either latitude/longitude ('lat' and 'lon') or geohash ('gh'). Results are ordered by ascending distance from the center.

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_nearby_poi"
  }
}

Input Schema

NameRequiredDescriptionDefault
ghNoGeohash location string (alternative to 'lat' and 'lon', e.g. from lookup_ip).
latNoLatitude in decimal WGS84 (provide both 'lat' and 'lon', or 'gh').
lonNoLongitude in decimal WGS84 (provide both 'lat' and 'lon', or 'gh').
distNoMaximum search distance from center in meters (default 1000, max 160000).
whatNoOptional preset POI category filter.
limitNoMaximum number of results to return (1 to 100, default 15).
filterNoOptional OpenStreetMap tag filters in 'key=value' format. Supports '*' wildcards and '~' prefix on value for case-insensitive matching (e.g. ['name=~*Sabores*', 'shop=bakery']).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior — results are ordered by ascending distance — but is silent on what happens when neither 'lat'/'lon' nor 'gh' is supplied, which matters because the schema lists zero required parameters.

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?

Two tight sentences with the location specification first and the result ordering last; nothing is redundant or buried. Every clause carries information.

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 seven optional parameters, a fully documented schema, and no output schema, the description supplies the essential frame: what a center point is, what the radius means, and how results are ordered. It does not address the absence of required parameters or what the result records contain, but nothing critical is missing for 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 the schema already documents every parameter, its units, defaults, and the 'what' enum. The description only restates the center-point alternatives and the meter-based radius, adding no syntax or selection guidance beyond the structured data — the baseline 3 applies.

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 ('Search for'), a precise resource ('geographical Points of Interest'), and the spatial scope (within a radius in meters around a center point). An agent immediately knows what the tool returns and in what order, and the sibling tools (get_balance, lookup_ip, validate_email) are unrelated enough that no explicit differentiation is needed.

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 establishes that the center may be given as lat/lon or as a geohash, which is real usage context, but it never says when to prefer one form over the other, nor when to use the 'what' preset category versus the free-form 'filter' tags. Usage is implied rather than prescribed.

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.

Resources