DaedalMap Geography Tools (loc_id)

Inspect Direct loc_id Connections

get_loc_id_info

Read-onlyIdempotent

Look up one known loc_id or a small batch in the selected reference graph. Return its identity and directly recorded loc_id connections, with family, direction, and relationship evidence. Each ID returns at most 50 connections and an explicit has_more flag. This tool does not expand descendants, infer containment, read shapes, search catalogs, or consult external adapters. No payment required.

Input Schema

TableJSON Schema

Name	Required	Description
`loc_id`	No	DaedalMap loc_id, e.g. 'USA-CA'.
`loc_ids`	No	Up to 10 known loc_ids, including a resolve_point stack.
`batch_id`	No	Optional caller-supplied batch id for tracing.
`request_id`	No	Optional caller-supplied request id for tracing.

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
`has_more`	No
`warnings`	No
`next_step`	No
`request_id`	No
`admin_level`	No
`connections`	No
`found_count`	No
`loc_id_count`	No
`clarification`	No
`meter_receipt`	No
`missing_count`	No
`connection_count`	No
`connection_limit`	No
`requested_loc_id`	No
`settlement_receipt`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed22 schema fields changedOct 16, 2026

removedInput schema / anyOf

Removed value: -[
-  {
-    "required": [
-      "loc_id"
-    ]
-  },
-  {
-    "required": [
-      "loc_ids"
-    ]
-  }
-]

addedInput schema / oneOf

Added value: +[
+  {
+    "required": [
+      "loc_id"
+    ]
+  },
+  {
+    "required": [
+      "loc_ids"
+    ]
+  }
+]

removedInput schema / properties / as_of

Removed 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"
-}

removedInput schema / properties / include_hierarchy

Removed value: -{
-  "description": "When true, include strict stored parent and ancestor data. This never invents a parent edge across mixed releases. Default false.",
-  "type": "boolean"
-}

removedInput schema / properties / include_references

Removed value: -{
-  "description": "When true, include known external or side-chain references attached to each loc_id. Default false.",
-  "type": "boolean"
-}

removedInput schema / properties / iso3

Removed value: -{
-  "description": "Optional country hint for crosswalk artifacts. Defaults to the loc_id country when possible.",
-  "type": "string"
-}

removedInput schema / properties / limit_per_system

Removed value: -{
-  "description": "Maximum overlap references to return per bridge/system. Default 10.",
-  "maximum": 100,
-  "minimum": 1,
-  "type": "integer"
-}

changedInput schema / properties / loc_ids / description

Previous value: -"DaedalMap loc_ids to inspect together, including every loc_id from a resolve_point stack. Default public cap is deployment-configurable."New value: +"Up to 10 known loc_ids, including a resolve_point stack."

addedInput schema / properties / loc_ids / maxItems
```
Added value: +10
```
addedInput schema / properties / loc_ids / minItems
```
Added value: +1
```

removedInput schema / properties / min_share

Removed value: -{
-  "description": "Optional minimum target-area share for reverse overlap references.",
-  "maximum": 1,
-  "minimum": 0,
-  "type": "number"
-}

removedInput schema / properties / systems

Removed 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"
-}

removedInput schema / properties / target_admin_level

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "integer"
-    }
-  ],
-  "description": "Admin level for crosswalk-backed reverse reference lookup. Inferred when omitted."
-}

addedOutput schema / properties / connection_count

Added value: +{
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / connection_limit

Added value: +{
+  "minimum": 1,
+  "type": "integer"
+}

addedOutput schema / properties / connections

Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

removedOutput schema / properties / data_packs
```
Removed value: -{
-  "type": "array"
-}
```
removedOutput schema / properties / geometry_families
```
Removed value: -{
-  "type": "array"
-}
```
addedOutput schema / properties / has_more
```
Added value: +{
+  "type": "boolean"
+}
```
removedOutput schema / properties / hierarchy
```
Removed value: -{
-  "type": "object"
-}
```
removedOutput schema / properties / next_calls
```
Removed value: -{
-  "type": "array"
-}
```
removedOutput schema / properties / references
```
Removed value: -{
-  "type": "object"
-}
```

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.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety burden is covered. The description still adds real behavioral context beyond them: a per-ID cap of 50 connections with an explicit has_more flag (pagination semantics), the silent-exclusion behaviors, and the note that no payment is required, which signals a possible paid path elsewhere.

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 operation and the return shape, then the scope exclusions, then the payment note. It is dense and nearly every clause earns its place; the exclusion list is somewhat long but directly serves disambiguation, which justifies the length.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. The description supplies the remaining missing pieces an agent needs to call this correctly: known-ID-only precondition, batch size, truncation limit, has_more signaling, and the explicit boundary against adjacent tools.

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 loc_id, loc_ids, batch_id and request_id are already documented, and the baseline is 3. The description only echoes the single-ID-or-batch shape; it adds no format, resolution or tracing semantics beyond what the schema states, and notably does not explain the 'resolve_point stack' behavior described in loc_ids.

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 (look up a loc_id or small batch in the selected reference graph) and defines the exact return payload: identity plus directly recorded connections with family, direction and evidence. The explicit negative scope ('does not expand descendants, infer containment, read shapes, search catalogs') cleanly separates it from siblings like get_geography, get_shape, and get_catalog.

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 establishes the usage condition well: it operates on known IDs only, supports a single ID or a batch, and explicitly refuses expansion, inference, shape reads, catalog search and adapter calls. It stops short of naming the sibling tools an agent should reach for instead when it does need shapes or catalog search, so routing is implied rather than explicit.

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) 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.