Skip to main content
Glama

DaedalMap Administrative Boundaries (loc_id to polygon)

by com.daedalmap

Get loc_id Geometry

get_geometry
Read-only

Shape retrieval for exact loc_ids, including loc_ids from any level of a resolve_point chain. Returns the requested geometry metadata, vintage, centroid, bounding box, and optional GeoJSON polygon. Historical geometry is returned first; an evidenced successor appears only as a separate question and is never substituted or fetched automatically. It does not explain hierarchy or crosswalks; use loc_id_info for those details. Prefer bbox/centroid unless exact rendering or clipping requires the polygon. No payment required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
loc_idNoDaedalMap loc_id, such as USA-CA-037, USA-Z-00601, USA-NWSFZ-AKZ317, EEZ-USA, or IHO1953-240001002.
loc_idsNoDaedalMap loc_ids to fetch in one call. Default public cap is deployment-configurable and lower when include_polygon is true.
batch_idNoOptional caller-supplied batch id for tracing.
request_idNoOptional caller-supplied request id for tracing.
include_polygonNoWhen true, include the full GeoJSON geometry. Default false.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • removedInput schema / properties / include_info
      Removed value: -{
-  "description": "When true for loc_ids batch mode, include heavier loc_id_info enrichment for each result. Default false for lean bulk geometry responses.",
-  "type": "boolean"
-}
  2. Changed1 schema field changed
    • addedInput schema / properties / include_info
      Added value: +{
+  "description": "When true for loc_ids batch mode, include heavier loc_id_info enrichment for each result. Default false for lean bulk geometry responses.",
+  "type": "boolean"
+}
  3. Added

TDQS

A4.9/5.0
Behavior5/5

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

The readOnlyHint annotation already signals safety, and the description adds meaningful context: historical geometry is returned first, an evidenced successor is never auto-substituted, and no payment is required. It also discloses a key limitation—no hierarchy or crosswalk explanation—which helps agents avoid misuse. No contradiction with annotations.

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?

Six short sentences, each carrying distinct information: scope, return values, historical behavior, limitation/alternative, preference guidance, and cost. It is front-loaded with the most important retrieval statement and contains no filler.

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?

Even though there is no output schema, the description clearly states what the tool returns, including metadata, vintage, centroid, bounding box, and optional GeoJSON polygon. It also covers behavior, cost, defaults, and routing to loc_id_info. An agent has enough context to select and invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds value by advising when to request the full polygon versus bbox/centroid, and by clarifying that loc_ids may come from any level of a resolve_point chain. That goes beyond the schema's examples without duplicating them.

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 opens with a specific verb and resource ('Shape retrieval for exact loc_ids') and enumerates the return contents: metadata, vintage, centroid, bounding box, and optional GeoJSON polygon. It explicitly distinguishes itself from loc_id_info by stating it does not explain hierarchy or crosswalks. An agent can tell this tool apart from its siblings without opening the schema.

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

Usage Guidelines5/5

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

It gives actionable direction to prefer bbox/centroid unless exact rendering or clipping requires the polygon, which effectively guides use of include_polygon. It names loc_id_info as the explicit alternative for hierarchy/crosswalk questions. The resolve_point chain scope also clarifies when this tool applies.

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

All DaedalMap Administrative Boundaries (loc_id to polygon) toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: discovery (get_catalog, get_pack), geometry retrieval (get_geometry), hierarchy (loc_id_info, resolve_loc_id_scope), relationship analysis (compare_geographies), preflight (check_geometry), export estimation and creation (estimate_geometry_package, create_geometry_export), job status (get_job_status), and help (get_tool_help). Even closely related tools like check_geometry and estimate_geometry_package address different concerns (shape availability vs export artifact), leaving no ambiguity.

Naming Consistency4/5

Most tools follow a consistent verb_noun pattern (check_geometry, compare_geographies, create_geometry_export, estimate_geometry_package, get_catalog, get_geometry, get_job_status, get_pack, get_tool_help, resolve_loc_id_scope). However, 'loc_id_info' breaks the pattern by being a noun phrase rather than a verb action, causing a minor deviation from the otherwise uniform convention.

Tool Count5/5

With 11 tools, the server covers the key operations for administrative boundary data—discovery, geometry retrieval, hierarchy navigation, comparison, export, and job management—without overreach. Each tool is necessary for a coherent workflow, and the count fits well within the typical 3-15 range for a domain-specific MCP server.

Completeness5/5

The tool set effectively covers the full lifecycle needed for administrative boundary use: discovery (catalog/pack), preflight checks, geometry retrieval, hierarchical navigation, relationship analysis, export estimation/creation, and job status. It includes essential utilities like get_tool_help for onboarding. No obvious gaps exist for the server's purpose; if anything, it is notably thorough for read/export operations.

Resources