DaedalMap Disaster and Geospatial Data

Resolve Reference to loc_id

resolve_reference

Read-only

Free geography utility. Converts one value, or a bounded list of values, from an external or adjacent geographic reference system into the DaedalMap loc_id universe. Examples: from_system='zip' value='00601'; from_system='nws_fire' value='AKZ317'; from_system='admin_boundary' value='Fairfax County'. Returns ranked loc_id matches with bridge vintage, overlap weights, and provenance where applicable. Historical references are returned as requested; an evidenced successor is a separate optional question and is never substituted automatically. No payment required.

Input Schema

TableJSON Schema

Name	Required	Description
`iso3`	No	Country hint for system-specific crosswalks. Default USA.
`as_of`	No	ISO date or year used to select a time-bounded identity assertion, especially for historical names and codes.
`items`	No	Reference values to resolve in one call. Default public cap is deployment-configurable.
`limit`	No	Maximum ranked matches to return. Default 10.
`value`	No	Identifier or name in the input system. Examples: 00601, USA-Z-00601, AKZ317, USA-NWSFZ-AKZ317, Fairfax County, Mediterranean Sea.
`batch_id`	No	Optional caller-supplied batch id for tracing.
`min_share`	No	Optional minimum area-share threshold for overlap matches.
`request_id`	No	Optional caller-supplied request id for tracing.
`from_system`	No	Input reference system, such as loc_id, census_geoid/us_census_geoid, admin_boundary, zip, zcta, overlay_zcta, nws_zone, nws_fire, overlay_nws_fire_weather_zone, tribal, water_body, marine_eez, nuts, historical_country/iso3166_3, or a catalog family id.
`country_hint`	No	Optional country hint for admin/name resolution.
`admin_level_hint`	No	Optional admin-level hint for admin/name resolution.
`target_admin_level`	No	Admin target level for crosswalk-backed resolution. Default admin_2. Accepts admin_0..admin_5, 0..5, or names such as country, state, county, tract, block_group, or block.
`relationship_vintage`	No	Optional relationship vintage to require, such as usa_geometry_current or census_2020_relationship_files.

Schema Changelog

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

Changed6 schema fields changedAug 26, 2026

removedInput schema / properties / bridge_vintage

Removed value: -{
-  "description": "Optional bridge vintage to require, such as usa_geometry_current or census_2020_relationship_files.",
-  "type": "string"
-}

changedInput schema / properties / iso3 / description

Previous value: -"Country hint for system-specific bridges. Default USA."New value: +"Country hint for system-specific crosswalks. Default USA."

removedInput schema / properties / items / items / properties / bridge_vintage

Removed value: -{
-  "description": "Optional bridge vintage for this row.",
-  "type": "string"
-}

addedInput schema / properties / items / items / properties / relationship_vintage

Added value: +{
+  "description": "Optional relationship vintage for this row.",
+  "type": "string"
+}

addedInput schema / properties / relationship_vintage

Added value: +{
+  "description": "Optional relationship vintage to require, such as usa_geometry_current or census_2020_relationship_files.",
+  "type": "string"
+}

changedInput schema / properties / target_admin_level / description

Previous value: -"Admin target level for bridge-backed resolution. Default admin_2. Accepts admin_0..admin_5, 0..5, or names such as country, state, county, tract, block_group, or block."New value: +"Admin target level for crosswalk-backed resolution. Default admin_2. Accepts admin_0..admin_5, 0..5, or names such as country, state, county, tract, block_group, or block."

Changed1 schema field changedAug 14, 2026

changedInput schema / properties / from_system / description

Previous value: -"Input reference system, such as loc_id, admin_boundary, zip, zcta, overlay_zcta, nws_zone, nws_fire, overlay_nws_fire_weather_zone, tribal, water_body, marine_eez, nuts, historical_country/iso3166_3, or a catalog family id."New value: +"Input reference system, such as loc_id, census_geoid/us_census_geoid, admin_boundary, zip, zcta, overlay_zcta, nws_zone, nws_fire, overlay_nws_fire_weather_zone, tribal, water_body, marine_eez, nuts, historical_country/iso3166_3, or a catalog family id."

Changed3 schema fields changedAug 10, 2026

addedInput schema / properties / as_of

Added value: +{
+  "description": "ISO date or year used to select a time-bounded identity assertion, especially for historical names and codes.",
+  "type": "string"
+}

changedInput schema / properties / from_system / description

Previous value: -"Input reference system, such as loc_id, admin_boundary, zip, zcta, overlay_zcta, nws_zone, nws_fire, overlay_nws_fire_weather_zone, tribal, water_body, marine_eez, nuts, or a catalog family id."New value: +"Input reference system, such as loc_id, admin_boundary, zip, zcta, overlay_zcta, nws_zone, nws_fire, overlay_nws_fire_weather_zone, tribal, water_body, marine_eez, nuts, historical_country/iso3166_3, or a catalog family id."

addedInput schema / properties / items / items / properties / as_of

Added value: +{
+  "description": "ISO date or year used to select a time-bounded identity assertion.",
+  "type": "string"
+}

Changed4 schema fields changedAug 8, 2026

addedInput schema / anyOf

Added value: +[
+  {
+    "required": [
+      "from_system",
+      "value"
+    ]
+  },
+  {
+    "required": [
+      "items"
+    ]
+  }
+]

addedInput schema / properties / batch_id

Added value: +{
+  "description": "Optional caller-supplied batch id for tracing.",
+  "type": "string"
+}

addedInput schema / properties / items

Added value: +{
+  "description": "Reference values to resolve in one call. Default public cap is deployment-configurable.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "admin_level_hint": {
+        "description": "Optional admin-level hint for admin/name resolution.",
+        "maximum": 5,
+        "minimum": 0,
+        "type": "integer"
+      },
+      "bridge_vintage": {
+        "description": "Optional bridge vintage for this row.",
+        "type": "string"
+      },
+      "country_hint": {
+        "description": "Optional country hint for admin/name resolution.",
+        "type": "string"
+      },
+      "from_system": {
+        "description": "Input reference system for this row. Defaults to top-level from_system when omitted.",
+        "type": "string"
+      },
+      "id": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "string"
+          }
+        ],
+        "description": "Optional caller identifier echoed in the result."
+      },
+      "iso3": {
+        "description": "Optional country hint for this row.",
+        "type": "string"
+      },
+      "limit": {
+        "description": "Maximum ranked matches for this row.",
+        "maximum": 100,
+        "minimum": 1,
+        "type": "integer"
+      },
+      "min_share": {
+        "description": "Optional minimum area-share threshold for this row.",
+        "maximum": 1,
+        "minimum": 0,
+        "type": "number"
+      },
+      "row_index": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "string"
+          }
+        ],
+        "description": "Optional caller row identifier echoed in the result."
+      },
+      "target_admin_level": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "integer"
+          }
+        ],
+        "description": "Optional admin target level for this row."
+      },
+      "value": {
+        "description": "Identifier or name in the input system.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "value"
+    ],
+    "type": "object"
+  },
+  "minItems": 1,
+  "type": "array"
+}

removedInput schema / required

Removed value: -[
-  "from_system",
-  "value"
-]

AddedAug 3, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The readOnlyHint annotation already indicates a safe read operation, so the bar is lower. The description adds useful behavior: output includes ranked loc_id matches with bridge vintage, overlap weights, and provenance, and historical values are not automatically replaced by successors. This goes beyond what annotations provide.

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?

The core purpose is front-loaded and the examples are compact and useful. There is minor redundancy: 'Free geography utility' and 'No payment required' convey nearly the same information, and the historical-reference sentence could be tighter, but overall the description is well structured.

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?

Given the readOnlyHint annotation and a 100%-covered schema with 13 parameters, the description covers the essential behavioral context: it explains the conversion, gives examples, and describes the return fields (ranked matches, bridge vintage, overlap weights, provenance). It does not describe pagination or response structure, but the schema and annotation carry much of the needed load.

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%, so baseline is 3. The examples in the description (from_system='zip' value='00601', from_system='nws_fire' value='AKZ317') largely repeat examples already present in the schema, so the description adds only minimal parameter-level meaning beyond the input schema.

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 action (converts one value or a bounded list into the DaedalMap loc_id universe) and names the exact resource and outcome. The concrete examples for zip, nws_fire, and admin_boundary clearly distinguish this from siblings like convert_reference or identify_reference_system.

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?

The description gives clear context for when to use the tool: resolving external or adjacent geographic values into loc_id. It also notes that historical references are returned as requested and that an evidenced successor is never substituted automatically, which is an implicit when-not. However, it does not explicitly name sibling tools or state when to prefer them over this tool.

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

All DaedalMap Disaster and Geospatial Data tools Inspect

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

A3.9/5.0

Disambiguation4/5

Most tools have clearly distinct scopes with detailed 'Use this' guidance, but a few pairs like get_disaster_link_chain and get_disaster_links_for_event, or query_dataset versus the specialized get_* event tools, could cause momentary confusion. Overall, descriptions mitigate overlap well.

Naming Consistency4/5

The majority follow a consistent verb_noun pattern (check_, compare_, convert_, create_, estimate_, get_, list_, resolve_). Minor exceptions like loc_id_info and query_dataset are acceptable but break the pattern slightly.

Tool Count3/5

28 tools exceed the preferred range, but the broad domain spanning disasters, geospatial geometry, reference conversion, and export jobs justifies many of them. Still, the count feels heavy and might overwhelm agents.

Completeness5/5

The tool surface is remarkably comprehensive: discovery (catalog, pack, geometry catalog), resolution (point, reference, scope), geometry (check, get, compare), conversion (quote, create, status), and disaster events for multiple types. No critical dead ends for the stated domain.

Resolve Reference to loc_id

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources