daedal-map

Overview Schema Source Related Servers Discussions Admin

Inspect One Selected Pack or Geometry Family

get_pack

Read-onlyIdempotent

Inspect a data pack or geometry family for lite details, full metadata, or a raw download URL. Follow the returned next_step to retrieve data or use the preferred geometry tool.

Instructions

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.

Changed6 schema fields changedSep 24, 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"
+}

addedInput schema / properties / detail

Added value: +{
+  "default": "lite",
+  "description": "Use lite to decide and start, full for detailed MCP query metadata, or download for the complete raw metadata file.",
+  "enum": [
+    "lite",
+    "full",
+    "download"
+  ],
+  "type": "string"
+}

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 from get_catalog. Newly catalog-admitted packs require no MCP schema change."

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 / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": true,
+  "anyOf": [
+    {
+      "required": [
+        "catalog",
+        "pack_id",
+        "detail"
+      ]
+    },
+    {
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "properties": {
+    "catalog": {
+      "enum": [
+        "data",
+        "geometry"
+      ],
+      "type": "string"
+    },
+    "clarification": {
+      "type": "object"
+    },
+    "detail": {
+      "enum": [
+        "lite",
+        "full",
+        "download"
+      ],
+      "type": "string"
+    },
+    "download_call": {
+      "type": "object"
+    },
+    "download_url": {
+      "type": "string"
+    },
+    "error": {
+      "additionalProperties": true,
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "details": {
+          "type": "object"
+        },
+        "message": {
+          "type": "string"
+        },
+        "retry_hint": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "code",
+        "message"
+      ],
+      "type": "object"
+    },
+    "full_call": {
+      "type": "object"
+    },
+    "guidance": {
+      "type": "object"
+    },
+    "material_policy": {
+      "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"
+    },
+    "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"
+}

First observedv1.0.0Jun 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds behavioral value by revealing that results include a next_step for progression and that detail levels map to lite vs full metadata vs download URL. 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?

Two tight sentences front-load the core purpose and then give the key follow-up behavior. There is no filler or redundant restatement of the schema.

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?

With a rich input schema and an output schema, the description covers the essential workflow and progression. The only mild gap is that 'preferred geometry tool' is not named explicitly, but the sibling list and schema make the intended routing reasonably discoverable.

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 all parameters in detail. The description adds only mild semantic framing ('lite starter contract') and mostly restates the detail-level behavior already present in the schemas.

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 uses a specific verb, 'Inspect', and a specific resource, 'one selected data pack or geometry family', and names three progressive modes (lite, full, download). It also differentiates from siblings by framing get_pack as operating on a single selected item while get_catalog lists and get_data retrieves data.

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?

The description gives actionable guidance: use it to inspect a selected pack, and then 'Use its next_step to retrieve data or call the preferred geometry tool.' It implies a sequential workflow but does not explicitly state when to prefer get_data or get_catalog instead, so it falls just short of full exclusion guidance.

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

Deploy Server