Skip to main content
Glama

DaedalMap Geography Tools (loc_id)

by com.daedalmap

Get loc_id / Chain Details

loc_id_info
Read-only

The drill-down tool for loc_ids returned by resolve_point and other geography calls. Pass one loc_id, or pass the point result's stack loc_ids together, to retrieve metadata, strict stored parentage, shape status, vintage/lifecycle fields, and child counts. Historical records are returned as requested; when an evidenced successor exists, supersession separately asks whether the caller wants it and never substitutes or fetches it automatically. Set include_hierarchy for the strict same-release ancestor chain and include_references for external or side-chain crosswalks. This is where detailed chain explanation belongs; resolve_point intentionally stays compact. For exact polygons use get_geometry, and for overlap or successor analysis use compare_geographies. No payment required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
iso3NoOptional country hint for crosswalk artifacts. Defaults to the loc_id country when possible.
loc_idNoDaedalMap loc_id, e.g. 'USA-CA'.
loc_idsNoDaedalMap loc_ids to inspect together, including every loc_id from a resolve_point stack. Default public cap is deployment-configurable.
systemsNoOptional reference systems to include when include_references is true, such as zcta, nws_fire, overlay_tribal, or overlay_nws_public_zone.
batch_idNoOptional caller-supplied batch id for tracing.
min_shareNoOptional minimum target-area share for reverse overlap references.
request_idNoOptional caller-supplied request id for tracing.
limit_per_systemNoMaximum overlap references to return per bridge/system. Default 10.
include_hierarchyNoWhen true, include strict stored parent and ancestor data. This never invents a parent edge across mixed releases. Default false.
include_referencesNoWhen true, include known external or side-chain references attached to each loc_id. Default false.
target_admin_levelNoAdmin level for crosswalk-backed reverse reference lookup. Inferred when omitted.

Schema Changelog

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

  1. Changed2 schema fields changed
    • changedInput schema / properties / iso3 / description
      Previous value: -"Optional country hint for bridge artifacts. Defaults to the loc_id country when possible."New value: +"Optional country hint for crosswalk artifacts. Defaults to the loc_id country when possible."
    • changedInput schema / properties / target_admin_level / description
      Previous value: -"Admin level for bridge-backed reverse reference lookup. Inferred when omitted."New value: +"Admin level for crosswalk-backed reverse reference lookup. Inferred when omitted."
  2. Changed2 schema fields changed
    • changedInput schema / properties / include_hierarchy / description
      Previous value: -"When true, include parent and full ancestor chain. Default false."New value: +"When true, include strict stored parent and ancestor data. This never invents a parent edge across mixed releases. Default false."
    • changedInput schema / properties / loc_ids / description
      Previous value: -"DaedalMap loc_ids to inspect in one call. Default public cap is deployment-configurable."New value: +"DaedalMap loc_ids to inspect together, including every loc_id from a resolve_point stack. Default public cap is deployment-configurable."
  3. Changed11 schema fields changed
    • addedInput schema / anyOf
      Added value: +[
+  {
+    "required": [
+      "loc_id"
+    ]
+  },
+  {
+    "required": [
+      "loc_ids"
+    ]
+  }
+]
    • addedInput schema / properties / batch_id
      Added value: +{
+  "description": "Optional caller-supplied batch id for tracing.",
+  "type": "string"
+}
    • addedInput schema / properties / include_hierarchy
      Added value: +{
+  "description": "When true, include parent and full ancestor chain. Default false.",
+  "type": "boolean"
+}
    • addedInput schema / properties / include_references
      Added value: +{
+  "description": "When true, include known external or side-chain references attached to each loc_id. Default false.",
+  "type": "boolean"
+}
    • addedInput schema / properties / iso3
      Added value: +{
+  "description": "Optional country hint for bridge artifacts. Defaults to the loc_id country when possible.",
+  "type": "string"
+}
    • addedInput schema / properties / limit_per_system
      Added value: +{
+  "description": "Maximum overlap references to return per bridge/system. Default 10.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / loc_ids
      Added value: +{
+  "description": "DaedalMap loc_ids to inspect in one call. Default public cap is deployment-configurable.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / min_share
      Added value: +{
+  "description": "Optional minimum target-area share for reverse overlap references.",
+  "maximum": 1,
+  "minimum": 0,
+  "type": "number"
+}
    • addedInput schema / properties / systems
      Added value: +{
+  "description": "Optional reference systems to include when include_references is true, such as zcta, nws_fire, overlay_tribal, or overlay_nws_public_zone.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / target_admin_level
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "integer"
+    }
+  ],
+  "description": "Admin level for bridge-backed reverse reference lookup. Inferred when omitted."
+}
    • removedInput schema / required
      Removed value: -[
-  "loc_id"
-]
  4. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses important behavioral traits: historical records are returned only as requested, an evidenced successor is never substituted or fetched automatically, and the caller is separately asked whether supersession is wanted. It also clarifies that hierarchy is 'strict same-release ancestor chain' and does not invent parent edges across mixed releases.

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?

The description is front-loaded with the tool's purpose and remains compact despite covering usage, alternatives, key flags, and behavioral caveats. Every sentence earns its place, and the alternative routing is stated efficiently without redundancy.

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?

For an 11-parameter tool with no output schema, the description covers the essential context: what the tool returns, how loc_ids should be passed, how historical/supersession behavior works, which flags control hierarchy/references, and which sibling tools handle other cases. Combined with the 100%-covered parameter schema, an agent has enough information to 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 schema already documents all parameters. The description adds meaningful semantic nuance: loc_ids can be passed as 'the point result's stack loc_ids together,' include_hierarchy means the 'strict same-release ancestor chain,' and include_references covers 'external or side-chain crosswalks.' This goes beyond the baseline without needing to re-document every parameter.

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 names a specific resource and action: it is 'the drill-down tool for loc_ids returned by resolve_point and other geography calls' and lists exactly what it retrieves: metadata, parentage, shape status, vintage/lifecycle fields, and child counts. It also differentiates itself from siblings by saying 'This is where detailed chain explanation belongs; resolve_point intentionally stays compact.'

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?

The description gives explicit usage context and alternative routing: use this tool for loc_id drill-downs and chain explanation, use get_geometry for exact polygons, and use compare_geographies for overlap or successor analysis. It also tells the caller to set include_hierarchy and include_references for specific needs, making the when-to-use decision clear.

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

All DaedalMap Geography Tools (loc_id) 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.2/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: point resolution, reference conversion, hierarchy traversal, geometry retrieval, export creation, job estimation, catalog discovery, and relationship comparison are all separated. The descriptions explicitly state what each tool does and what it does not do, preventing misselection. Even closely related tools like get_geometry, get_geometry_export, and estimate_geometry_package are differentiated by their roles (single-shape retrieval vs. export artifact vs. dry-run estimate).

Naming Consistency5/5

All 20 tool names follow a consistent verb_noun snake_case pattern (e.g., get_geometry, create_conversion_job, resolve_point, list_reference_systems). The verbs are action-oriented (get, create, estimate, resolve, compare, list, read) and each noun clearly indicates the subject. While a few like 'loc_id_info' and 'how_geometry_works' deviate slightly from the strict verb_noun structure, they still fit the overall style and are easy to predict.

Tool Count4/5

The 20 tools are slightly above the typical 3-15 range but still well-scoped for a comprehensive geocoding and geography service. The extra tools reflect the breadth of operations offered (discovery, conversion, estimation, export, resolution, relationship analysis), each earning its place. The count feels reasonable given the domain, though it approaches the upper boundary of what an agent might easily navigate.

Completeness5/5

The tool surface covers the full lifecycle of geocoding workflows: discovery (get_catalog, get_pack, read_geometry_catalog), point resolution (resolve_point), reference resolution (resolve_reference), identifier identification (identify_reference_system), hierarchy traversal (resolve_loc_id_scope, loc_id_info), geometry retrieval (get_geometry), relationship analysis (compare_geographies), conversion (convert_reference, create_conversion_job), export (create_geometry_export), and estimation (estimate_geometry_package, estimate_conversion_job). The inclusion of help tools (get_tool_help, how_geometry_works) and job status retrieval ensures no dead ends. The absence of destructive or update operations is consistent with a read-only geospatial data service, so the surface is appropriate.

Resources