DaedalMap Volcanic Activity

List Published Packs or Geographies

get_catalog

Read-onlyIdempotent

Choose data or geometry to list published pack IDs or family and scope IDs. The response includes a complete catalog download URL. Use get_pack for data or get_geography for geometry. 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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "catalog": "<catalog>"
    },
    "name": "get_catalog"
  }
}

Input Schema

Name	Required	Description	Default
`catalog`	Yes	Required directory selector.

Output Schema

Name	Required	Description	Default
`error`	No
`packs`	No
`detail`	No
`reason`	No
`scopes`	No
`catalog`	No
`families`	No
`guidance`	No
`warnings`	No
`next_step`	No
`pack_count`	No
`provenance`	No
`request_id`	No
`download_url`	No
`generated_at`	No
`clarification`	No
`result_status`	No
`tool_families`	No
`excluded_count`	No
`resolved_query`	No
`catalog_version`	No
`uncertain_count`	No
`uncertain_packs`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedOct 16, 2026

removedInput schema / properties / catalog / default
```
Removed value: -"data"
```

changedInput schema / properties / catalog / description

Previous value: -"Catalog family. The geography facade defaults to geometry; other facades default to data."New value: +"Required directory selector."

removedInput schema / properties / country_scope

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

removedInput schema / properties / detail

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

removedInput schema / properties / loc_id

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

removedInput schema / properties / time_range

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

addedInput schema / required
```
Added value: +[
+  "catalog"
+]
```

changedOutput schema / anyOf

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

addedOutput schema / properties / excluded_count

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

addedOutput schema / properties / families

Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / resolved_query
```
Added value: +{
+  "type": "object"
+}
```
addedOutput schema / properties / result_status
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / scopes

Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / uncertain_count

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

addedOutput schema / properties / uncertain_packs

Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

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

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description's only behavioral addition is that the response carries a catalog download URL, which is already implied by the output schema; the long paragraph about worldwide coverage and per-country releases is scope marketing rather than behavioral disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The actionable content (what it lists, the download URL, the get_pack/get_geography routing) is front-loaded, but it is then buried under a lengthy 'Current catalog' paragraph listing 252 entities and eight countries that does nothing for tool selection or invocation.

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?

With annotations covering safety and an output schema covering returns, the description only needs to explain the selector and routing, which it mostly does. However, the undefined 'scope IDs' terminology and the routing to a non-sibling tool leave small gaps for an agent deciding between catalog and pack calls.

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

Parameters4/5

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

Schema coverage is 100% and the enum values are self-explanatory, so the baseline is 3. The description goes beyond this by mapping each enum value to a distinct return shape ('data' yields pack IDs, 'geometry' yields family and scope IDs), which genuinely adds meaning over the schema.

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?

It names a specific verb ('list') and resource ('published pack IDs or family and scope IDs') and ties the output to the required catalog selector. It is distinguishable from the generic get_data/get_pack siblings, though the phrase 'family and scope IDs' is jargon that is never defined.

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?

It gives explicit routing: 'Use get_pack for data or get_geography for geometry,' which tells the agent when to pick this tool over an alternative. The weakness is that get_geography is not among the listed siblings, so the routing target is ambiguous for the agent.

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.