DaedalMap Disaster and Geospatial Data

Inspect Known loc_id Identities

get_loc_id_info

Read-onlyIdempotent

Known-place navigation and enrichment tool: use only when you already have one canonical loc_id or a bounded loc_ids array. It returns identity, strict stored parentage, lifecycle, shape status, and place-specific data-pack and geometry-family availability with executable next calls. Supply as_of for a precision-aware source-release date review alert. It does not list the global catalog and does not return polygon coordinates; use get_catalog to browse everything or get_geometry for shapes. Set include_hierarchy for same-release ancestors and include_references for maintained external or cross-family connections. Historical records are never replaced automatically. No payment required.

Input Schema

TableJSON Schema

Name	Required	Description
`iso3`	No	Optional country hint for crosswalk artifacts. Defaults to the loc_id country when possible.
`as_of`	No	Optional ISO day, month, or year (YYYY-MM-DD, YYYY-MM, or YYYY). Reviews the current Full source edition and returns a Double-check date alert for coarse or stale coverage; it does not select historical geometry.
`loc_id`	No	DaedalMap loc_id, e.g. 'USA-CA'.
`loc_ids`	No	DaedalMap loc_ids to inspect together, including every loc_id from a resolve_point stack. Default public cap is deployment-configurable.
`systems`	No	Optional reference systems to include when include_references is true, such as zcta, nws_fire, overlay_tribal, or overlay_nws_public_zone.
`batch_id`	No	Optional caller-supplied batch id for tracing.
`min_share`	No	Optional minimum target-area share for reverse overlap references.
`request_id`	No	Optional caller-supplied request id for tracing.
`limit_per_system`	No	Maximum overlap references to return per bridge/system. Default 10.
`include_hierarchy`	No	When true, include strict stored parent and ancestor data. This never invents a parent edge across mixed releases. Default false.
`include_references`	No	When true, include known external or side-chain references attached to each loc_id. Default false.
`target_admin_level`	No	Admin level for crosswalk-backed reverse reference lookup. Inferred when omitted.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	No
`iso3`	No
`name`	No
`error`	No
`family`	No
`loc_id`	No
`reason`	No
`results`	No
`batch_id`	No
`guidance`	No
`warnings`	No
`hierarchy`	No
`next_step`	No
`data_packs`	No
`next_calls`	No
`references`	No
`request_id`	No
`admin_level`	No
`found_count`	No
`loc_id_count`	No
`clarification`	No
`meter_receipt`	No
`missing_count`	No
`requested_loc_id`	No
`geometry_families`	No
`settlement_receipt`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 6, 2026

addedInput schema / properties / as_of

Added value: +{
+  "description": "Optional ISO day, month, or year (YYYY-MM-DD, YYYY-MM, or YYYY). Reviews the current Full source edition and returns a Double-check date alert for coarse or stale coverage; it does not select historical geometry.",
+  "type": "string"
+}

Changed1 schema field changedSep 24, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": true,
+  "anyOf": [
+    {
+      "required": [
+        "loc_id"
+      ]
+    },
+    {
+      "required": [
+        "loc_id_count",
+        "results"
+      ]
+    },
+    {
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "properties": {
+    "admin_level": {
+      "type": [
+        "string",
+        "integer",
+        "null"
+      ]
+    },
+    "batch_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "clarification": {
+      "type": "object"
+    },
+    "data_packs": {
+      "type": "array"
+    },
+    "error": {
+      "additionalProperties": true,
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "details": {
+          "type": "object"
+        },
+        "message": {
+          "type": "string"
+        },
+        "retry_hint": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "code",
+        "message"
+      ],
+      "type": "object"
+    },
+    "family": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "found_count": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "geometry_families": {
+      "type": "array"
+    },
+    "guidance": {
+      "type": "object"
+    },
+    "hierarchy": {
+      "type": "object"
+    },
+    "iso3": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "loc_id": {
+      "type": "string"
+    },
+    "loc_id_count": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "meter_receipt": {
+      "type": "object"
+    },
+    "missing_count": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "name": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "next_calls": {
+      "type": "array"
+    },
+    "next_step": {
+      "additionalProperties": true,
+      "anyOf": [
+        {
+          "required": [
+            "action"
+          ]
+        },
+        {
+          "required": [
+            "tool"
+          ]
+        }
+      ],
+      "properties": {
+        "action": {
+          "type": "string"
+        },
+        "arguments": {
+          "type": "object"
+        },
+        "tool": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "reason": {
+      "type": "string"
+    },
+    "references": {
+      "type": "object"
+    },
+    "request_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "requested_loc_id": {
+      "type": "string"
+    },
+    "results": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "error": {
+            "additionalProperties": true,
+            "properties": {
+              "code": {
+                "type": "string"
+              },
+              "details": {
+                "type": "object"
+              },
+              "message": {
+                "type": "string"
+              },
+              "retry_hint": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "code",
+              "message"
+            ],
+            "type": "object"
+          },
+          "id": {
+            "type": [
+              "string",
+              "integer",
+              "null"
+            ]
+          },
+          "ok": {
+            "type": "boolean"
+          },
+          "row_index": {
+            "type": [
+              "string",
+              "integer",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "settlement_receipt": {
+      "type": "object"
+    },
+    "warnings": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

AddedSep 21, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, yet the description still adds real behavioral context: 'Historical records are never replaced automatically,' 'This never invents a parent edge across mixed releases,' the deployment-configurable cap on loc_ids, and the as_of double-check alert. It stops short of describing response volume or failure modes, so 4 rather than 5.

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?

Front-loaded with the core routing condition and tightly packed with signal-dense clauses appropriate for a 12-parameter tool. The trailing 'No payment required' is a low-value aside, but the rest earns its space.

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?

With an output schema present and annotations covering safety, the description's job is routing, mode of use, and non-obvious behavior — all covered (entry condition, exclusions, as_of semantics, hierarchy edge guarantees, historical immutability). Nothing an agent needs to call it correctly is missing.

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 the schema already documents all 12 parameters and the baseline is 3. The description's notes on include_hierarchy ('same-release ancestors') and include_references ('maintained external or cross-family connections') largely restate what the schema fields already say, adding only marginal extra meaning.

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?

States a specific verb and resource ('returns identity, strict stored parentage, lifecycle, shape status, and place-specific data-pack and geometry-family availability') and explicitly contrasts itself with siblings get_catalog and get_geometry. The opening 'use only when you already have one canonical loc_id' frames the scope precisely, so an agent can distinguish it 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?

Gives both a positive trigger ('use only when you already have one canonical loc_id or a bounded loc_ids array') and explicit exclusions with named alternatives ('does not list the global catalog... use get_catalog to browse everything or get_geometry for shapes'). This is textbook when/when-not/alternative routing.

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.