DaedalMap Disaster and Geospatial Data

Convert Geographic Reference

convert_reference

Read-only

The single geographic reference converter. Converts one reference, or a bounded list, through DaedalMap loc_id: X -> loc_id -> Y. Omit to_system to enter the loc_id universe; provide it for any-to-any conversion. Use get_pack first when the family or country-specific system is unknown. No payment required.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`iso3`	No	Country hint for crosswalk artifacts. Default USA.
`as_of`	No	ISO date or year used for time-bounded identities.
`items`	No	Reference conversions to run in one call. Default public cap is deployment-configurable.
`limit`	No	Maximum ranked output references to return. Default 10.
`value`	No	Identifier or name in the input system.
`batch_id`	No	Optional caller-supplied batch id for tracing.
`min_share`	No	Optional minimum overlap share threshold.
`to_system`	No	Optional output reference system. Defaults to DaedalMap loc_id; provide zcta, nws_fire, overlay_nws_public_zone, overlay_tribal, admin_local, or another catalog system for any-to-any conversion.	daedalmap.loc_id
`request_id`	No	Optional caller-supplied request id for tracing.
`from_system`	No	Input reference system, such as zip, overlay_zcta, nws_fire, tribal, admin_boundary, or loc_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 level used as the intermediate crosswalk target. Default admin_2.
`relationship_vintage`	No	Optional source relationship vintage to require.

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedSep 21, 2026

changedInput schema / anyOf

Previous value: -[
-  {
-    "required": [
-      "from_system",
-      "value",
-      "to_system"
-    ]
-  },
-  {
-    "required": [
-      "items"
-    ]
-  }
-]New value: +[
+  {
+    "required": [
+      "from_system",
+      "value"
+    ]
+  },
+  {
+    "required": [
+      "items"
+    ]
+  }
+]

addedInput schema / properties / admin_level_hint

Added value: +{
+  "description": "Optional admin-level hint for admin/name resolution.",
+  "maximum": 6,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / as_of

Added value: +{
+  "description": "ISO date or year used for time-bounded identities.",
+  "type": "string"
+}

addedInput schema / properties / country_hint

Added value: +{
+  "description": "Optional country hint for admin/name resolution.",
+  "type": "string"
+}

addedInput schema / properties / items / items / properties / admin_level_hint

Added value: +{
+  "description": "Optional admin-level hint for admin/name resolution.",
+  "maximum": 6,
+  "minimum": 0,
+  "type": "integer"
+}

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

Added value: +{
+  "description": "ISO date or year used for time-bounded identities.",
+  "type": "string"
+}

addedInput schema / properties / items / items / properties / country_hint

Added value: +{
+  "description": "Optional country hint for admin/name resolution.",
+  "type": "string"
+}

addedInput schema / properties / to_system / default
```
Added value: +"daedalmap.loc_id"
```

changedInput schema / properties / to_system / description

Previous value: -"Output reference system, such as loc_id, zcta, nws_fire, overlay_nws_public_zone, overlay_tribal, admin_local, or admin_geometry."New value: +"Optional output reference system. Defaults to DaedalMap loc_id; provide zcta, nws_fire, overlay_nws_public_zone, overlay_tribal, admin_local, or another catalog system for any-to-any conversion."

Changed6 schema fields changedAug 26, 2026

removedInput schema / properties / bridge_vintage

Removed value: -{
-  "description": "Optional source bridge vintage to require.",
-  "type": "string"
-}

changedInput schema / properties / iso3 / description

Previous value: -"Country hint for bridge artifacts. Default USA."New value: +"Country hint for crosswalk artifacts. 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 source relationship vintage to require.",
+  "type": "string"
+}

changedInput schema / properties / target_admin_level / description

Previous value: -"Admin level used as the intermediate bridge target. Default admin_2."New value: +"Admin level used as the intermediate crosswalk target. Default admin_2."

Changed4 schema fields changedAug 8, 2026

addedInput schema / anyOf

Added value: +[
+  {
+    "required": [
+      "from_system",
+      "value",
+      "to_system"
+    ]
+  },
+  {
+    "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 conversions to run in one call. Default public cap is deployment-configurable.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "bridge_vintage": {
+        "description": "Optional bridge vintage for this row.",
+        "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 output references for this row.",
+        "maximum": 100,
+        "minimum": 1,
+        "type": "integer"
+      },
+      "min_share": {
+        "description": "Optional minimum overlap 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 intermediate admin target level for this row."
+      },
+      "to_system": {
+        "description": "Output reference system for this row. Defaults to top-level to_system when omitted.",
+        "type": "string"
+      },
+      "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",
-  "to_system"
-]

AddedAug 3, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Beyond the readOnlyHint annotation, the description discloses the internal X -> loc_id -> Y conversion chain, bounded-list handling, and the fact that no payment is required. It does not describe ranking or response details, but the read-only safety profile is already covered by 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?

Four short, front-loaded sentences with no wasted words. The core conversion model, routing advice, and payment note each earn their place, and there is no repetition of schema content.

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 14-parameter tool with no output schema, the description covers the essential call patterns, the prerequisite get_pack step, and the conversion output concept. It leaves ranking and detailed row behavior to the schema, which is complete, so the gaps are modest.

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 meaningful semantics for to_system by explaining the 'loc_id universe' and when to omit versus provide it, which goes beyond the field-level schema descriptions.

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 clearly names the action (converts a geographic reference) and the scope (one reference or a bounded list) with a specific conversion path through DaedalMap loc_id. It does not explicitly differentiate from siblings like create_conversion_job, though 'single converter' gestures at uniqueness.

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 explicit mode-selection guidance: omit to_system to enter the loc_id universe, provide it for any-to-any conversion, and use get_pack first when the family or country-specific system is unknown. This gives an agent actionable routing beyond what the schema provides.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Convert Geographic Reference

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources