daedal-map

Overview Schema Source Related Servers Discussions Admin

Resolve Point(s) (Deep)

resolve_deep_point

Read-onlyIdempotent

Refine WGS84 coordinates to deeper locations within a chosen geographic family. Uses a shallow_loc_id from resolve_point to return exact shape matches for administrative, marine, or other canonical families.

Instructions

Second-pass resolution for one WGS84 coordinate or a bounded point array. Supply one shared shallow_loc_id returned by resolve_point and one canonical family from get_catalog(catalog='geometry'). family defaults to administrative; shape-backed families use direct bbox-to-exact-shape lookup without crosswalks. Single and bulk requests share this scoped contract.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lat`	No	Latitude in WGS84 decimal degrees.
`lon`	No	Longitude in WGS84 decimal degrees.
`family`	No	One family selector. Defaults to administrative; use marine for the direct Marine resolver, or a canonical country family such as postal_area, watershed, or land_management_region.	administrative
`points`	No	Points already known to fall within the supplied shallow_loc_id scope.
`batch_id`	No	Optional caller-supplied batch id echoed for point arrays.
`request_id`	No	Optional caller-supplied request id for tracing.
`shallow_loc_id`	Yes	The deepest canonical Admin 1-3 loc_id returned by resolve_point, such as USA-NY-061-009903.
`target_admin_level`	No	Optional exact Admin 4-6 level. Omit for the deepest available match.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	No
`error`	No
`point`	No
`stack`	No
`family`	No
`reason`	No
`matched`	No
`results`	No
`batch_id`	No
`guidance`	No
`warnings`	No
`join_keys`	No
`next_step`	No
`request_id`	No
`point_count`	No
`clarification`	No
`family_result`	No
`meter_receipt`	No
`resolved_count`	No
`shallow_loc_id`	No
`deeper_available`	No
`overlap_families`	No
`unresolved_count`	No
`settlement_receipt`	No
`deepest_resolved_family`	No
`deepest_resolved_loc_id`	No
`deepest_resolved_admin_level`	No
`available_deeper_admin_levels`	No

Schema Changelog

Changes observed during successful MCP inspections.

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": [
+        "point",
+        "stack"
+      ]
+    },
+    {
+      "required": [
+        "point",
+        "family",
+        "family_result"
+      ]
+    },
+    {
+      "required": [
+        "point_count",
+        "results"
+      ]
+    },
+    {
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "properties": {
+    "available_deeper_admin_levels": {
+      "type": "array"
+    },
+    "batch_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "clarification": {
+      "type": "object"
+    },
+    "deeper_available": {
+      "type": "boolean"
+    },
+    "deepest_resolved_admin_level": {
+      "type": [
+        "string",
+        "integer",
+        "null"
+      ]
+    },
+    "deepest_resolved_family": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "deepest_resolved_loc_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "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"
+    },
+    "family_result": {
+      "type": "object"
+    },
+    "guidance": {
+      "type": "object"
+    },
+    "join_keys": {
+      "type": "object"
+    },
+    "matched": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "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"
+    },
+    "overlap_families": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "point": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {
+            "lat": {
+              "type": "number"
+            },
+            "lon": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "lat",
+            "lon"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "point_count": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "reason": {
+      "type": "string"
+    },
+    "request_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "resolved_count": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "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"
+    },
+    "shallow_loc_id": {
+      "type": "string"
+    },
+    "stack": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "unresolved_count": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "warnings": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

AddedSep 24, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds meaningful behavioral context: family defaults to administrative, shape-backed families use direct bbox-to-exact-shape lookup without crosswalks, and single and bulk requests share the same scoped contract. This goes beyond what annotations alone provide.

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?

Three dense sentences with no filler. The purpose is front-loaded, and each sentence adds distinct value: what it does, what inputs it needs, and how family selection affects behavior.

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 output schema and rich annotations, the description is largely sufficient. It covers the tool's role, prerequisites, defaults, and the shared single/bulk contract. Minor missing context includes explicit error or edge-case behavior, but this is not essential for correct tool selection and invocation.

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 description coverage is 100%, so the baseline is 3. The description adds value by explaining that family comes from get_catalog, defaults to administrative, and that shape-backed families bypass crosswalks. It also clarifies that shallow_loc_id is the output of resolve_point, giving provenance not fully captured in the 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 verb ('resolve') and resource ('one WGS84 coordinate or a bounded point array') and identifies itself as 'Second-pass resolution' relative to resolve_point. This clearly distinguishes it from sibling tools like resolve_point or get_geometry.

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 explicitly says to supply a shallow_loc_id returned by resolve_point and a family from get_catalog(catalog='geometry'), establishing clear prerequisites and context. It does not enumerate explicit when-not-to-use conditions or name alternative tools, but the second-pass framing makes the usage boundary clear.

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

Deploy Server