daedal-map

Overview Schema Source Related Servers Discussions Admin

Compare Geographic Identities

compare_geographies

Read-onlyIdempotent

Compare two known DaedalMap loc_ids to determine containment, no overlap, or unknown using reference-graph identity and direct relationship evidence, without reading polygons.

Instructions

Compare two known loc_ids using selected reference-graph identity and direct relationship evidence. Verified Admin ancestry can prove containment; a typed graph edge can prove only the relation it declares. An explicit negative edge returns no_overlap; a missing edge returns unknown. This tool never reads polygons or computes shape intersections. Use an external identifier bridge before this call when the input is not a loc_id. No payment required.

Input Schema

Name	Required	Description
`as_of`	No	ISO date or year applied to both identities.
`items`	No	Bounded geography pairs to compare in one call.
`batch_id`	No	Optional caller-supplied batch id for tracing.
`left_as_of`	No	Optional ISO date or year for the left identity; overrides as_of.
`request_id`	No	Optional caller-supplied request id for tracing.
`left_loc_id`	No	First DaedalMap loc_id.
`right_as_of`	No	Optional ISO date or year for the right identity; overrides as_of.
`right_loc_id`	No	Second DaedalMap loc_id.
`include_successors`	No	Include direct successors and present-day descendants for maintained historical identities. Default true.

Output Schema

Name	Required	Description	Default
`ok`	No
`error`	No
`reason`	No
`results`	No
`batch_id`	No
`guidance`	No
`warnings`	No
`next_step`	No
`item_count`	No
`request_id`	No
`failed_count`	No
`clarification`	No
`meter_receipt`	No
`compared_count`	No
`graph_evidence`	No
`geometry_loaded`	No
`spatial_relation`	No
`temporal_relation`	No
`relationship_basis`	No
`settlement_receipt`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv1.0.3Nov 12, 2026

removedInput schema / anyOf

Removed value: -[
-  {
-    "required": [
-      "left_loc_id",
-      "right_loc_id"
-    ]
-  },
-  {
-    "required": [
-      "items"
-    ]
-  }
-]

addedInput schema / oneOf

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

addedInput schema / properties / items / items / properties / left_loc_id / minLength
```
Added value: +1
```
addedInput schema / properties / items / items / properties / right_loc_id / minLength
```
Added value: +1
```
addedInput schema / properties / left_loc_id / minLength
```
Added value: +1
```
addedInput schema / properties / right_loc_id / minLength
```
Added value: +1
```
addedOutput schema / properties / geometry_loaded
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / graph_evidence

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

addedOutput schema / properties / relationship_basis
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedv1.0.1Sep 24, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": true,
+  "anyOf": [
+    {
+      "required": [
+        "ok",
+        "spatial_relation"
+      ]
+    },
+    {
+      "required": [
+        "item_count",
+        "results"
+      ]
+    },
+    {
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "properties": {
+    "batch_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "clarification": {
+      "type": "object"
+    },
+    "compared_count": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "error": {
+      "additionalProperties": true,
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "details": {
+          "type": "object"
+        },
+        "message": {
+          "type": "string"
+        },
+        "retry_hint": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "code",
+        "message"
+      ],
+      "type": "object"
+    },
+    "failed_count": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "guidance": {
+      "type": "object"
+    },
+    "item_count": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "meter_receipt": {
+      "type": "object"
+    },
+    "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"
+    },
+    "request_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "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"
+    },
+    "spatial_relation": {
+      "type": [
+        "string",
+        "object",
+        "null"
+      ]
+    },
+    "temporal_relation": {
+      "type": [
+        "string",
+        "object",
+        "null"
+      ]
+    },
+    "warnings": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

AddedSep 24, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description goes well beyond them by explaining the epistemics of the result: verified Admin ancestry proves containment, a typed edge proves only its declared relation, a negative edge yields no_overlap, a missing edge yields unknown. It also discloses a resource constraint (no polygon/shape computation) and that no payment is required, which annotations cannot express.

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?

Five tight sentences, front-loaded with purpose and immediately followed by result semantics and the input precondition. Each sentence carries distinct information — no restatement of the title or the name, and even the trailing 'No payment required' removes a real doubt about a network-backed lookup.

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 a read-only comparison tool with a full output schema, the description supplies exactly the missing piece: how to interpret the outcome (containment vs. declared relation vs. no_overlap vs. unknown) and what inputs are valid. Nothing an agent needs to decide whether and how to call it is absent.

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 every parameter including as_of, left_as_of/right_as_of, include_successors, and the batch items array is already documented in the schema. The description adds the loc_id input requirement but says nothing about the temporal override semantics or the batch form, so it does not exceed the schema baseline.

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 first sentence states a specific verb and resource ('Compare two known loc_ids') plus the evidentiary basis used ('reference-graph identity and direct relationship evidence'). The negative clause 'never reads polygons or computes shape intersections' cleanly separates it from the resolve_* and get_shape siblings without needing their names.

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?

It gives an explicit precondition for use: 'Use an external identifier bridge before this call when the input is not a loc_id,' which tells the agent when this tool is the wrong entry point. It does not name the specific bridging sibling, so the agent must still infer which of convert_reference/identify_* to chain, but the when-to-use and when-not context is otherwise unambiguous.

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

Deploy Server