Skip to main content
Glama

Find Nearby Points of Interest

search_pois
Read-only

Find restaurants, fuel, groceries, attractions near a location, or search by POI name. POIs carry no ratings — rank and describe them by what they are and how close they are.

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

Input Schema

NameRequiredDescriptionDefault
qNoSearch POI by name
limitNo
categoryNo
locationNoLocation name (fuzzy). Required unless q is provided.
location_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one genuinely non-obvious trait — that POIs carry no ratings and should be ranked/described by type and distance — but says nothing about result ordering, pagination, or how limit interacts with the result set.

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?

Two sentences, both front-loaded with the search capability first and the ranking caveat second. Tight and waste-free, though the second sentence's phrasing ('by what they are and how close they are') is a slightly indirect way to state the ordering rule.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter, 40%-covered tool with no output schema, the description omits how location_id relates to location, what limit does, and what a result entry contains. It is adequate for the core purpose but incomplete on the details an agent needs to call it correctly.

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 40%, so the description must carry weight, and it does map its phrasing to the q, location and category parameters. It still leaves location_id (and its precedence over location) and the limit default/behavior unexplained, so it only partially compensates for the coverage gap.

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 concrete verb (Find) plus the resource and its categories (restaurants, fuel, groceries, attractions), and covers two distinct modes: proximity search and name lookup. It distinguishes itself from detail-oriented siblings like get_poi_details implicitly, but never names an alternative sibling (search_locations, get_poi_details) to confirm the boundary.

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 two usage modes ('near a location' vs 'search by POI name') and mentions the category axis, which is useful implied guidance. However, it gives no explicit when-to-use versus search_locations or get_poi_details, and no prerequisites or exclusions.

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.