Skip to main content
Glama

Find a place

search_places
Read-onlyIdempotent

Finds a place by name (a city, district, street or full address) and returns up to six matches, best first, each with coordinates and, for areas, a bounding box. Use to get the coordinates or the area of a place for a building lookup or an area search. It finds places only in the countries baseray holds buildings for; a place in another country returns no match, and that country can be requested at https://baseray.tech/countries.

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

Input Schema

NameRequiredDescriptionDefault
queryYesThe place to find, as a person would write it, e.g. "Cluj-Napoca", "Strada Memorandumului 28, Cluj-Napoca" or "Brno-střed".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, and closed-world behavior, so the bar is low, yet the description still adds real substance: a cap of six results, best-match-first ordering, bounding boxes for areas, and the geographic coverage restriction that silently yields 'no match'. That coverage caveat is exactly the kind of failure mode an agent cannot infer from annotations or schema.

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?

Three sentences, front-loaded with what it does and returns, then the use case, then the coverage caveat. No filler, no repetition of the title, and the exception is placed last where it belongs.

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

Completeness5/5

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

With no output schema, the description compensates by describing the return payload (up to six matches, ordered, coordinates, bounding boxes for areas) and the empty-result condition. For a one-parameter read tool this is complete enough that an agent can call it and interpret the response without further help.

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% and the single 'query' parameter already carries a rich description with format examples, so the baseline of 3 applies. The description's 'a city, district, street or full address' largely restates what the schema examples demonstrate, adding little new syntax or constraint information.

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 and resource ('Finds a place by name') plus the accepted name forms (city, district, street, full address) and the result shape (up to six matches, best first, with coordinates/bounding box). This clearly separates it from siblings like find_buildings/search_buildings, which resolve buildings rather than place names.

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

Usage Guidelines4/5

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

Explicitly frames the intended downstream uses ('to get the coordinates or the area of a place for a building lookup or an area search') and states a hard when-not condition: places outside the covered countries return no match, with a URL to check coverage. It does not name sibling tools to use instead for other lookup needs, so it stops short of a full routing guide.

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