DaedalMap Disaster and Geospatial Data

Get Pack

get_pack

Read-onlyIdempotent

Inspect one selected data pack or geometry family progressively: lite starter contract, full MCP query metadata, or a raw metadata download URL. Use its next_step to retrieve data or call the preferred geometry tool.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`detail`	No	Use lite to decide and start, full for detailed MCP query metadata, or download for the complete raw metadata file.	lite
`catalog`	No	Metadata family. When omitted, geometry facades default to geometry and known geometry-family ids are inferred; all other calls default to data.
`pack_id`	Yes	Pack identifier from get_catalog. Newly catalog-admitted packs require no MCP schema change.
`release_unit`	No	Optional non-country geometry release unit such as GLOBAL or MARINE. Do not combine with country_scope.
`country_scope`	No	Optional ISO3 country for a geometry family. Omit it to learn which countries publish the family; provide it for country-specific versions, vintages, levels, and artifacts.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No
`detail`	No
`reason`	No
`catalog`	No
`pack_id`	No
`sources`	No
`guidance`	No
`warnings`	No
`full_call`	No
`next_step`	No
`provenance`	No
`request_id`	No
`download_url`	No
`clarification`	No
`download_call`	No
`material_policy`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedSep 21, 2026

addedInput schema / properties / catalog

Added value: +{
+  "description": "Metadata family. When omitted, geometry facades default to geometry and known geometry-family ids are inferred; all other calls default to data.",
+  "enum": [
+    "data",
+    "geometry"
+  ],
+  "type": "string"
+}

addedInput schema / properties / country_scope

Added value: +{
+  "description": "Optional ISO3 country for a geometry family. Omit it to learn which countries publish the family; provide it for country-specific versions, vintages, levels, and artifacts.",
+  "pattern": "^[A-Za-z]{3}$",
+  "type": "string"
+}

changedInput schema / properties / detail / description

Previous value: -"Use lite for normal discovery. Use full only for one selected pack when its complete public metadata is required."New value: +"Use lite to decide and start, full for detailed MCP query metadata, or download for the complete raw metadata file."

changedInput schema / properties / detail / enum

Previous value: -[
-  "lite",
-  "full"
-]New value: +[
+  "lite",
+  "full",
+  "download"
+]

addedInput schema / properties / release_unit

Added value: +{
+  "description": "Optional non-country geometry release unit such as GLOBAL or MARINE. Do not combine with country_scope.",
+  "pattern": "^[A-Za-z0-9_-]+$",
+  "type": "string"
+}

changedOutput schema / anyOf

Previous value: -[
-  {
-    "required": [
-      "pack_id"
-    ]
-  },
-  {
-    "required": [
-      "error"
-    ]
-  }
-]New value: +[
+  {
+    "required": [
+      "catalog",
+      "pack_id",
+      "detail"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / catalog

Added value: +{
+  "enum": [
+    "data",
+    "geometry"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / detail

Added value: +{
+  "enum": [
+    "lite",
+    "full",
+    "download"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / download_call
```
Added value: +{
+  "type": "object"
+}
```
addedOutput schema / properties / download_url
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / full_call
```
Added value: +{
+  "type": "object"
+}
```

addedOutput schema / properties / next_step / anyOf

Added value: +[
+  {
+    "required": [
+      "action"
+    ]
+  },
+  {
+    "required": [
+      "tool"
+    ]
+  }
+]

removedOutput schema / properties / next_step / required
```
Removed value: -[
-  "action"
-]
```

Changed1 schema field changedSep 20, 2026

addedInput schema / properties / detail

Added value: +{
+  "default": "lite",
+  "description": "Use lite for normal discovery. Use full only for one selected pack when its complete public metadata is required.",
+  "enum": [
+    "lite",
+    "full"
+  ],
+  "type": "string"
+}

Changed1 schema field changedSep 13, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": true,
+  "anyOf": [
+    {
+      "required": [
+        "pack_id"
+      ]
+    },
+    {
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "properties": {
+    "clarification": {
+      "type": "object"
+    },
+    "error": {
+      "additionalProperties": true,
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "details": {
+          "type": "object"
+        },
+        "message": {
+          "type": "string"
+        },
+        "retry_hint": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "code",
+        "message"
+      ],
+      "type": "object"
+    },
+    "guidance": {
+      "type": "object"
+    },
+    "material_policy": {
+      "type": "object"
+    },
+    "next_step": {
+      "additionalProperties": true,
+      "properties": {
+        "action": {
+          "type": "string"
+        },
+        "arguments": {
+          "type": "object"
+        },
+        "tool": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "action"
+      ],
+      "type": "object"
+    },
+    "pack_id": {
+      "type": "string"
+    },
+    "provenance": {
+      "type": "object"
+    },
+    "reason": {
+      "type": "string"
+    },
+    "request_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "sources": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "warnings": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedAug 26, 2026

changedInput schema / properties / pack_id / description

Previous value: -"Pack identifier such as 'currency', 'earthquakes', 'floods', 'hurricanes', 'tornadoes', 'tsunamis', 'un_sdg', 'volcanoes', 'world_factbook', or 'worldpop'."New value: +"Pack identifier from get_catalog. Newly catalog-admitted packs require no MCP schema change."

Changed1 schema field changedJun 11, 2026

changedInput schema / properties / pack_id / description

Previous value: -"Pack identifier such as 'currency', 'earthquakes', 'volcanoes', 'tsunamis', 'hurricanes', 'un_sdg', 'world_factbook', or 'worldpop'."New value: +"Pack identifier such as 'currency', 'earthquakes', 'floods', 'hurricanes', 'tornadoes', 'tsunamis', 'un_sdg', 'volcanoes', 'world_factbook', or 'worldpop'."

Changed1 schema field changedMay 17, 2026

changedInput schema / properties / pack_id / description

Previous value: -"Pack identifier such as 'currency', 'earthquakes', 'volcanoes', 'tsunamis', 'hurricanes', 'un_sdg', or 'world_factbook'."New value: +"Pack identifier such as 'currency', 'earthquakes', 'volcanoes', 'tsunamis', 'hurricanes', 'un_sdg', 'world_factbook', or 'worldpop'."

Changed1 schema field changedApr 22, 2026

changedInput schema / properties / pack_id / description

Previous value: -"Pack identifier such as 'currency', 'earthquakes', 'volcanoes', or 'tsunamis'."New value: +"Pack identifier such as 'currency', 'earthquakes', 'volcanoes', 'tsunamis', 'hurricanes', 'un_sdg', or 'world_factbook'."

First observedApr 10, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, and non-destructive behavior. The description adds useful behavioral context beyond those hints: the progressive lite/full/download contract and the presence of a next_step handoff for further action.

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?

The description is compact and front-loaded with the core purpose, followed by the handoff behavior. Some jargon like 'starter contract' and 'preferred geometry tool' is vague, but the overall structure is efficient.

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?

Rich schema descriptions, an output schema, and safety annotations cover most operational details. The description still leaves the sibling relationship slightly implicit: it would be stronger if it explicitly named get_data or get_catalog and positioned get_pack in the workflow.

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 pack_id, detail, catalog, release_unit, and country_scope are already well documented. The description restates the detail modes ('lite starter contract, full MCP query metadata, raw metadata download URL') but adds no new parameter-level meaning beyond 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 names a concrete verb+resource ('inspect one selected data pack or geometry family') and enumerates the three detail modes: lite, full, and download. 'Inspect' plus the reference to next_step separates it from catalog listing and direct data retrieval tools.

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?

The description implies a workflow: inspect a selected pack, then use next_step to retrieve data or call the preferred geometry tool. It never explicitly names get_catalog or get_data as alternatives, nor states when not to use this tool, leaving sibling routing implicit.

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.

Get Pack

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources