Skip to main content
Glama

geocode_place

Read-only

Resolve a free-text place name to a bounding box via Nominatim.

Returns ``{"bbox": [min_lon, min_lat, max_lon, max_lat], "display_name":
...}`` so the agent can inspect the box before searching, or pass it
straight to ``search_catalog``'s ``bbox``.

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": "geocode_place"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesFree-text place name to resolve with Nominatim.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / query / description
      Added value: +"Free-text place name to resolve with Nominatim."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description earns credit for disclosing the external Nominatim dependency, which hints at network calls and provider rate/usage constraints. It does not describe failure or ambiguity behavior (unknown place, multiple matches), which would matter for an agent deciding whether to retry or refine the query.

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 short sentences, front-loaded with the purpose and followed by the return shape and how to consume it. The return-shape restatement is slightly redundant given an output schema exists, but it is framed usefully as guidance on what to do with the box.

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 one-parameter read-only lookup with a full output schema, the description covers purpose, provider, return value, and downstream use. Only the handling of ambiguous or failed lookups is absent, a modest gap for a tool this simple.

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% for the single query parameter, and the description's phrase "free-text place name" merely restates the schema wording. No additional hints about accepted formats (city, country, address string) or disambiguation syntax are added, so the baseline of 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?

The description states a specific verb and resource ("Resolve a free-text place name to a bounding box") and names the backing service (Nominatim), so the transformation performed is unambiguous. By saying the box can be passed to search_catalog's bbox, it also implicitly positions itself relative to the closest sibling rather than leaving the agent to guess.

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?

It gives clear usage context: call this to obtain a bbox either for manual inspection or as direct input to search_catalog. It stops short of explicit when-not-to-use guidance (e.g. when you already have coordinates, or when the place is ambiguous) and names no alternative resolution path.

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.