Skip to main content
Glama

Cerca luoghi

search_places
Read-onlyIdempotent

Find places around coordinates. Groups: outdoors, heritage, family, all. Opening hours and accessibility are unverified source data. Results include source attribution and public DalVivo URLs.

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": {
      "lat": "<lat>",
      "lng": "<lng>"
    },
    "name": "search_places"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYes
lngYes
groupNoall
limitNo
cursorNo
radius_mNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: opening hours and accessibility are unverified source data, and results carry source attribution and public DalVivo URLs. It still omits pagination behavior for the cursor and the practical consequence of the 30km default radius.

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?

Four short sentences, front-loaded with the core action and with no filler or repetition. The data-quality caveat and result-content note each earn their place, though the group list is somewhat redundant with the schema enum.

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 six-parameter geo-search tool with no output schema, the description covers data trustworthiness and result contents well. It stops short of explaining pagination, result ordering, and how the large default radius affects results, which an agent needs to call it well.

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% across six parameters, so the description must carry parameter meaning and largely does not. It implies lat/lng by saying "around coordinates" and repeats the group enum values, but limit (max 10), cursor, and radius_m (default 30km, max 100km) are completely unexplained, leaving the most consequential tuning parameters opaque.

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?

"Find places around coordinates" names a specific verb and resource with a clear scope, and the group enumeration signals this is a discovery/search tool rather than a single-record fetch like get_place. It never explicitly contrasts itself with siblings such as get_place or resolve_location, so differentiation is inferred rather than stated.

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?

The description gives no when-to-use or when-not-to-use guidance: nothing says to call get_place for a single known place, resolve_location to turn an address into coordinates, or search_events/search_day_plans for those resource types. The only selection hint is the list of group values, which is a filter, not usage guidance.

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