Skip to main content
Glama

Find a place

find_place
Read-only

Find Spanish places by name (municipality, district, neighbourhood, province, region, postal code ...) and their place_id for search.

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

Input Schema

NameRequiredDescriptionDefault
kindNoonly this kind, e.g. municipality, district, neighbourhood
nameYese.g. 'Chamberí', 'Marbella', 'Valle de Arán'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the useful fact that the output carries a place_id intended to feed search, but it does not say whether multiple matches are returned, how ambiguity between same-named places is handled, or whether the search is exact or fuzzy. Modest added value over the annotations.

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?

A single front-loaded sentence with no filler; the resource and the returned identifier come first. The closing construction "and their place_id for search" is slightly compressed and could be clearer, but nothing is wasted.

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?

For a simple two-parameter read tool with full schema coverage, annotations, and no output schema, the description covers what is searched, the supported kinds, and the key returned field. Only the multi-match/ambiguity behavior is left unstated, a minor gap at this complexity level.

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 coverage is 100%, so both parameters are already documented with examples ('Chamberí', 'Marbella', 'Valle de Arán'). The description's list of kinds slightly extends the kind parameter's schema examples (adding province, region, postal code), but adds no matching semantics such as accent handling or partial-name support. Baseline 3 applies.

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 Spanish places by name" gives a specific verb and resource, and the parenthetical enumerates the supported place kinds (municipality, district, neighbourhood, province, region, postal code). It also signals the return value (place_id) and its downstream use for search. It does not explicitly distinguish itself from siblings like find_parcel or get_place_facts, which keeps it at 4.

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 phrase "and their place_id for search" implies the use case: resolve a place name to an ID before a search call. However, there is no explicit statement of when to prefer this over find_parcel or get_place_facts, and no mention of what to do when no match is found. Usage is implied rather than stated.

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