daedal-map

Overview Schema Source Related Servers Discussions Admin

Resolve Map Viewport (Deep)

resolve_deep_bbox

Read-onlyIdempotent

Resolve a rectangle’s deep administrative overlaps inside a shallow loc_id by routing to that country’s exact Admin 1-6 partition. Supply four WGS84 corners; zoom in for broad views.

Instructions

Second-pass rectangle overlap within one returned shallow administrative loc_id. Routes to that country's one Admin 1-owned exact partition and compares its Admin 1-6 spine. Supply the original four WGS84 corners; broad views may require zooming in.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "corners": "<corners>",
      "shallow_loc_id": "<shallow_loc_id>"
    },
    "name": "resolve_deep_bbox"
  }
}

Input Schema

Name	Required	Description
`corners`	Yes	Four distinct corners of one axis-aligned rectangle; no antimeridian crossing.
`request_id`	No	Optional caller-supplied tracing ID.
`shallow_loc_id`	Yes	One canonical Admin 1-3 loc_id from the shallow result; its Admin 1 owner selects one deep partition.

Output Schema

Name	Required	Description	Default
`ok`	No
`bbox`	No
`error`	No
`reason`	No
`ranking`	No
`batch_id`	No
`guidance`	No
`warnings`	No
`next_step`	No
`best_match`	No
`request_id`	No
`query_layout`	No
`admin_1_scope`	No
`clarification`	No
`meter_receipt`	No
`shallow_loc_id`	No
`geometry_release`	No
`settlement_receipt`	No
`matches_by_admin_level`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.0.3Nov 12, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds genuine structural behavior ('routes to that country's one Admin 1-owned exact partition') and a practical caveat that broad viewports may need to be narrowed, but leaves error behavior and the difference in returned granularity vs. the shallow pass unstated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with the second-pass framing front-loaded, but the middle sentence is dense and low-information ('compares its Admin 1-6 spine'), and the opening is a noun phrase rather than a clear action verb, costing immediate comprehension.

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 and full annotation coverage, the description carries only the burden of explaining intent and routing; it does so sufficiently, noting the second-pass nature, the dependency on a prior shallow loc_id, and the viewport-size caveat. No critical calling information 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 coverage is 100%, so the schema already documents corners, shallow_loc_id, and request_id. The description reinforces that the four corners must be the 'original' WGS84 corners of the same rectangle, which is a mild but real addition about reusing the first-pass input; otherwise it adds nothing beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the operation as a 'second-pass rectangle overlap' constrained to 'one returned shallow administrative loc_id,' which distinguishes it from the shallow sibling, but the core phrasing ('compares its Admin 1-6 spine', 'exact partition') is opaque jargon that does not state in plain terms that it refines a viewport into an exact deep administrative match.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Second-pass' plus 'one returned shallow administrative loc_id' implies this must be called after the shallow lookup, and 'broad views may require zooming in' hints at a failure mode. However, it never states the prerequisite explicitly (e.g., 'call resolve_bbox first') nor names when to prefer resolve_deep_point or the shallow variant.

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

Deploy Server