Skip to main content
Glama
Overture Maps MCP server

Overture Maps MCP server

search_divisions

Read-onlyIdempotent

Look up countries, regions, counties, and localities by name in Overture Maps, optionally narrowing results by country, subtype, or admin level.

Instructions

Look up administrative divisions (countries, regions, counties, localities) in Overture Maps. Search by name (e.g. 'Springfield'), optionally narrowed by country, subtype (country, region, county, locality, ...) or admin_level. Geometry is omitted by default to save space; set include_geometry=true only if you specifically need the boundary polygon.

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

Input Schema

NameRequiredDescriptionDefault
latNo
lngNo
nameNoDivision name to search for, e.g. 'Paris', 'Bavaria'.
limitNoNumber of results (default 10, max 50).
radiusNo
countryNoISO country code to narrow the search, e.g. FR.
subtypeNoDivision subtype: country, region, county, locality, etc.
admin_levelNoAdministrative level (0 = country, higher = more local).
include_geometryNoInclude the boundary polygon (large). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.5
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the behavioral default that geometry is omitted to save space, which is useful but restates the include_geometry schema note. It says nothing about result volume, rate limits, or how missing/ambiguous names are resolved.

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?

Two sentences, front-loaded with the resource and search strategy, then the geometry cost warning. No filler and nothing repeated that the agent does not need at selection time.

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 9-parameter, annotation-covered, read-only search tool with no output schema, the description covers purpose, filtering strategy and the expensive optional field adequately. The gap is the undocumented lat/lng/radius trio, which leaves one of the tool's two search modes unexplained.

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 67%, so the baseline is 3. The description reinforces the meaning of name, country, subtype and admin_level, but lat, lng and radius have no descriptions anywhere and the description never explains that they enable a proximity search — the most opaque part of the schema goes unaddressed.

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?

The description gives a specific verb and resource ('Look up administrative divisions') and enumerates the domain (countries, regions, counties, localities) in Overture Maps, which lets an agent separate it from search_places or find_buildings by resource type. It stops short of explicitly contrasting with the sibling tools, but the resource scoping is unambiguous.

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?

It states how to search ('by name... optionally narrowed by country, subtype or admin_level') and gives one explicit conditional rule: set include_geometry=true only if you specifically need the boundary polygon. There is no guidance on when to prefer this over search_places, nor on when a proximity search (lat/lng/radius) is the right entry point rather than a name search.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.