daedal-map

Overview Schema Source Related Servers Discussions Admin

List Available Packs and Geometry Families

get_catalog

Read-onlyIdempotent

Discover data packs or geometry families by place, time, or country. Select lite, full, or download detail to filter and choose a pack for further retrieval.

Instructions

Discover data packs or geometry families progressively: lite selection, full metric/query inventory, or a raw catalog download URL. Choose one result and call get_pack next.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`detail`	No	Use lite to select a pack, full for expanded metric/query inventories, or download for the complete raw catalog URL.	lite
`loc_id`	No	Optional DaedalMap loc_id for catalog='data'. Combine with time_range to discover packs confirmed for both place and time. For place details without pack filtering, use get_loc_id_info.
`catalog`	No	Catalog family. The geography facade defaults to geometry; other facades default to data.	data
`time_range`	No	Optional inclusive discovery window for catalog='data'. At least one bound is required.
`country_scope`	No	Optional ISO3 focus for catalog='geometry' with detail='lite'.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No
`packs`	No
`detail`	No
`reason`	No
`catalog`	No
`guidance`	No
`warnings`	No
`next_step`	No
`pack_count`	No
`provenance`	No
`request_id`	No
`download_url`	No
`generated_at`	No
`clarification`	No
`tool_families`	No
`catalog_version`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 24, 2026

addedInput schema / properties / catalog

Added value: +{
+  "default": "data",
+  "description": "Catalog family. The geography facade defaults to geometry; other facades default to data.",
+  "enum": [
+    "data",
+    "geometry"
+  ],
+  "type": "string"
+}

addedInput schema / properties / country_scope

Added value: +{
+  "description": "Optional ISO3 focus for catalog='geometry' with detail='lite'.",
+  "type": "string"
+}

addedInput schema / properties / detail

Added value: +{
+  "default": "lite",
+  "description": "Use lite to select a pack, full for expanded metric/query inventories, or download for the complete raw catalog URL.",
+  "enum": [
+    "lite",
+    "full",
+    "download"
+  ],
+  "type": "string"
+}

addedInput schema / properties / loc_id

Added value: +{
+  "description": "Optional DaedalMap loc_id for catalog='data'. Combine with time_range to discover packs confirmed for both place and time. For place details without pack filtering, use get_loc_id_info.",
+  "type": "string"
+}

addedInput schema / properties / time_range

Added value: +{
+  "additionalProperties": false,
+  "description": "Optional inclusive discovery window for catalog='data'. At least one bound is required.",
+  "properties": {
+    "end": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "integer"
+        }
+      ]
+    },
+    "start": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "integer"
+        }
+      ]
+    }
+  },
+  "type": "object"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": true,
+  "anyOf": [
+    {
+      "required": [
+        "catalog",
+        "detail"
+      ]
+    },
+    {
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "properties": {
+    "catalog": {
+      "enum": [
+        "data",
+        "geometry"
+      ],
+      "type": "string"
+    },
+    "catalog_version": {
+      "type": "string"
+    },
+    "clarification": {
+      "type": "object"
+    },
+    "detail": {
+      "enum": [
+        "lite",
+        "full",
+        "download"
+      ],
+      "type": "string"
+    },
+    "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"
+    },
+    "generated_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "guidance": {
+      "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_count": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "packs": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "provenance": {
+      "type": "object"
+    },
+    "reason": {
+      "type": "string"
+    },
+    "request_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "tool_families": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "warnings": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedv1.0.0Jun 10, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds behavioral context by explaining that the tool returns progressively richer selections (lite, full, or download URL) and acts as a precursor to get_pack. No contradiction exists.

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 sentences with no filler. The first sentence front-loads the tool's purpose and the three output levels; the second sentence provides the immediate next action. Every word earns its place.

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 rich input schema, output schema, and annotations, the description is adequately complete for a discovery tool. It could optionally mention that no parameters are required or clarify conditional defaults (e.g., catalog defaults to data), but these are already structured in the schema, so the minimal gap does not impede correct usage.

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?

Input schema coverage is 100%, with each parameter already documented. The description adds minor semantic alignment by mapping 'lite selection', 'full metric/query inventory', and 'raw catalog download URL' to the detail enum, but does not go beyond the schema to enrich parameter understanding.

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 and resource: 'Discover data packs or geometry families' and elaborates the three progressive detail modes (lite/full/download). It also names the next step 'call get_pack next', which distinguishes this discovery tool from its siblings.

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

Usage Guidelines5/5

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

The description explicitly tells the agent to choose a result and call get_pack next, establishing the intended flow. Additionally, the loc_id parameter description routes to get_loc_id_info when pack filtering is not needed, providing a clear when-not alternative.

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

Deploy Server