DaedalMap Volcanic Activity

List Available Packs and Geometry Families

get_catalog

Read-onlyIdempotent

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. Current catalog: The same geography tools work worldwide across a cataloged baseline of 252 geographic entities, reaching up to Admin 2. Where additional country releases are available, the same calls automatically return deeper administrative tiers or maintained reference families. Additional detail is currently available for Australia, Brazil, Canada, France, Germany, Mexico, United Kingdom, United States.

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.

Changed2 schema fields changedSep 23, 2026

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"
+}

Changed9 schema fields changedSep 21, 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"
+}

changedOutput schema / anyOf

Previous value: -[
-  {
-    "required": [
-      "packs"
-    ]
-  },
-  {
-    "required": [
-      "error"
-    ]
-  }
-]New value: +[
+  {
+    "required": [
+      "catalog",
+      "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_url
```
Added value: +{
+  "type": "string"
+}
```

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 13, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": true,
+  "anyOf": [
+    {
+      "required": [
+        "packs"
+      ]
+    },
+    {
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "properties": {
+    "catalog_version": {
+      "type": "string"
+    },
+    "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"
+    },
+    "generated_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "guidance": {
+      "type": "object"
+    },
+    "next_step": {
+      "additionalProperties": true,
+      "properties": {
+        "action": {
+          "type": "string"
+        },
+        "arguments": {
+          "type": "object"
+        },
+        "tool": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "action"
+      ],
+      "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 observedApr 16, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description doesn't repeat those. It adds valuable behavioral context: the tool automatically returns deeper administrative tiers for certain countries, and the progressive discovery behavior. This goes beyond annotations and helps the agent understand the tool's adaptive output.

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 first sentence is efficient and front-loaded, stating the core function and the three discovery levels. The second sentence gives workflow guidance. The second paragraph adds catalog scope context, which is useful but slightly verbose. Overall, it's well-structured and each sentence 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 tool's complexity (5 optional parameters, nested object, enums) and the presence of an output schema, the description is complete. It explains the catalog's geographic scope and the progressive workflow, which the schema does not. It doesn't need to cover return values because the output schema exists. The description provides sufficient context for correct invocation.

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 each parameter already has clear documentation. The main description doesn't add parameter-specific semantics beyond the workflow context (e.g., progressive detail levels), which the schema already explains. This meets the baseline of 3 for high coverage.

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 clearly states the tool's purpose: to discover data packs or geometry families with progressive levels (lite, full, download). It distinguishes itself from get_pack by explicitly routing the agent to call get_pack next, and from get_data by focusing on catalog listing rather than data retrieval. The verb 'discover' and resource 'catalog' are specific.

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 provides a clear workflow: start with lite to select a pack, then call get_pack. It also mentions that get_loc_id_info is the alternative for place details without pack filtering (in the parameter description). However, it doesn't explicitly state when not to use this tool versus get_data or get_tool_help, though the workflow implication is strong.

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

All DaedalMap Volcanic Activity 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.