DaedalMap Disaster and Geospatial Data

Discover or Read Geography Coverage

get_geography

Read-onlyIdempotent

Inspect one published geometry family across scopes or one scope across families. Returns coverage and known editions from catalog metadata only. Optional year selects the latest admitted edition no later than that year when the selected catalog has an edition index; an unavailable index is reported explicitly.

Input Schema

Name	Required	Description	Default
`page`	No
`year`	No
`scope_id`	No
`family_id`	No
`page_size`	No
`include_geometry`	No

Output Schema

Name	Required	Description	Default
`error`	No
`reason`	No
`catalog`	No
`coverage`	No
`guidance`	No
`scope_id`	No
`warnings`	No
`family_id`	No
`next_step`	No
`provenance`	No
`request_id`	No
`admin_spine`	No
`clarification`	No
`requested_year`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 31, 2026

addedInput schema / anyOf

Added value: +[
+  {
+    "required": [
+      "family_id"
+    ]
+  },
+  {
+    "required": [
+      "scope_id"
+    ]
+  }
+]

removedInput schema / oneOf

Removed value: -[
-  {
-    "required": [
-      "family_id"
-    ]
-  },
-  {
-    "required": [
-      "scope_id"
-    ]
-  }
-]

addedInput schema / properties / include_geometry
```
Added value: +{
+  "type": "boolean"
+}
```

addedInput schema / properties / page

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

addedInput schema / properties / page_size

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

AddedOct 16, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered. The description adds genuine behavioral context beyond that: results come 'from catalog metadata only', and an unavailable edition index is 'reported explicitly' rather than silently ignored. It does not explain pagination behavior or how include_geometry interacts with the 'metadata only' claim, leaving a real ambiguity for a tool that exposes a geometry flag.

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?

Three sentences, each carrying distinct information: what is inspected, what is returned and its source, and how year filters. Front-loaded with the core action. Slightly dense in domain shorthand but no filler sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 structure need not be described, and the description covers the year-selection edge case. However, with 6 parameters at 0% schema coverage and an unexplained include_geometry flag that tensions with 'catalog metadata only', the definition is not quite sufficient for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 6 parameters, so the description must compensate and only partly does. It clarifies the year parameter's selection rule ('latest admitted edition no later than that year') well, but page, page_size, include_geometry, and the family_id/scope_id pairing are left entirely to bare type constraints.

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

Purpose4/5

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

States a concrete verb ('Inspect') and a specific resource ('one published geometry family across scopes or one scope across families'), and the 'one ... vs across' phrasing implicitly contrasts with the bulk sibling compare_geographies. It never names a sibling explicitly, and the jargon ('geometry family', 'scope', 'admitted edition') assumes domain familiarity, so an agent must infer the boundary rather than read it.

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

Usage Guidelines2/5

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

There is no statement of when to prefer this over get_catalog, get_shape, identify_dataset_geography, or compare_geographies, and no prerequisites or exclusions. The only usage signal is implicit: it inspects catalog-level coverage, not geometry payloads. An agent has to derive the routing decision from the description's vocabulary alone.

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.