DaedalMap Volcanic Activity

Get Data

get_data

Read-onlyIdempotent

Retrieve rows from one selected published data pack using exact metrics, loc_id-based region filters, time/metric filters, sorting, and a row limit. Disaster event rows include stable event_id values for get_event drill-down. A parent administrative loc_id selects matching descendant rows at the pack's published grain. Call get_pack first; geometry families use their focused next-step tools.

Input Schema

TableJSON Schema

Name	Required	Description
`sort`	No	Sort by a sortable field from get_pack; direction defaults to asc.
`limit`	No	Maximum number of rows to return for the requested source or pack.
`output`	No	Optional response controls. v1 supports rows only.
`filters`	Yes
`metrics`	Yes	Exact metric ids from get_pack. Use event_count for aggregate counts only when get_pack publishes it.
`pack_id`	Yes	Pack identifier from get_catalog. Newly catalog-admitted packs require no MCP schema change.
`request_id`	No	Optional caller-supplied request id for tracing and idempotency.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`rows`	No
`sort`	No
`error`	No
`limit`	No
`reason`	No
`pack_id`	No
`guidance`	No
`warnings`	No
`next_step`	No
`row_count`	No
`source_id`	No
`truncated`	No
`provenance`	No
`query_mode`	No
`request_id`	No
`capability_id`	No
`clarification`	No
`filters_applied`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 16, 2026

changedInput schema / properties / filters / additionalProperties

Previous value: -{
-  "anyOf": [
-    {
-      "type": [
-        "string",
-        "number",
-        "integer",
-        "boolean",
-        "null"
-      ]
-    },
-    {
-      "items": {
-        "type": [
-          "string",
-          "number",
-          "integer",
-          "boolean"
-        ]
-      },
-      "type": "array"
-    }
-  ]
-}New value: +false

Changed13 schema fields changedSep 24, 2026

addedInput schema / properties / filters / additionalProperties

Added value: +{
+  "anyOf": [
+    {
+      "type": [
+        "string",
+        "number",
+        "integer",
+        "boolean",
+        "null"
+      ]
+    },
+    {
+      "items": {
+        "type": [
+          "string",
+          "number",
+          "integer",
+          "boolean"
+        ]
+      },
+      "type": "array"
+    }
+  ]
+}

removedInput schema / properties / filters / description

Removed value: -"Structured filters including time, region_ids, and compare clauses."

addedInput schema / properties / filters / properties

Added value: +{
+  "compare": {
+    "description": "Threshold filters using filterable fields or selected metric ids published by get_pack.",
+    "items": {
+      "additionalProperties": false,
+      "properties": {
+        "field": {
+          "minLength": 1,
+          "type": "string"
+        },
+        "op": {
+          "enum": [
+            "=",
+            "!=",
+            ">",
+            ">=",
+            "<",
+            "<="
+          ],
+          "type": "string"
+        },
+        "value": {}
+      },
+      "required": [
+        "field",
+        "op",
+        "value"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "equals": {
+    "additionalProperties": {
+      "anyOf": [
+        {
+          "type": [
+            "string",
+            "number",
+            "integer",
+            "boolean",
+            "null"
+          ]
+        },
+        {
+          "items": {
+            "type": [
+              "string",
+              "number",
+              "integer",
+              "boolean"
+            ]
+          },
+          "type": "array"
+        }
+      ]
+    },
+    "description": "Exact field/value filters using filterable fields published by get_pack.",
+    "type": "object"
+  },
+  "region_ids": {
+    "description": "Canonical country or hierarchical loc_ids from get_pack, such as JPN or USA-TX.",
+    "items": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "minItems": 1,
+    "type": "array",
+    "uniqueItems": true
+  },
+  "time": {
+    "additionalProperties": false,
+    "anyOf": [
+      {
+        "required": [
+          "value"
+        ]
+      },
+      {
+        "required": [
+          "start"
+        ]
+      },
+      {
+        "required": [
+          "end"
+        ]
+      }
+    ],
+    "description": "Inclusive ISO-8601 date/datetime or integer-year selection. Use YYYY-MM-DD, not partial YYYY-MM strings.",
+    "properties": {
+      "end": {
+        "anyOf": [
+          {
+            "format": "date-time",
+            "type": "string"
+          },
+          {
+            "format": "date",
+            "type": "string"
+          },
+          {
+            "type": "integer"
+          }
+        ]
+      },
+      "granularity": {
+        "enum": [
+          "daily",
+          "weekly",
+          "monthly",
+          "yearly",
+          "timestamp"
+        ],
+        "type": "string"
+      },
+      "start": {
+        "anyOf": [
+          {
+            "format": "date-time",
+            "type": "string"
+          },
+          {
+            "format": "date",
+            "type": "string"
+          },
+          {
+            "type": "integer"
+          }
+        ]
+      },
+      "value": {
+        "anyOf": [
+          {
+            "format": "date-time",
+            "type": "string"
+          },
+          {
+            "format": "date",
+            "type": "string"
+          },
+          {
+            "type": "integer"
+          }
+        ]
+      }
+    },
+    "type": "object"
+  }
+}

changedInput schema / properties / metrics / description

Previous value: -"Metric ids to return. Use event_count for aggregate counts when supported."New value: +"Exact metric ids from get_pack. Use event_count for aggregate counts only when get_pack publishes it."

addedInput schema / properties / metrics / items / minLength
```
Added value: +1
```
addedInput schema / properties / metrics / minItems
```
Added value: +1
```
addedInput schema / properties / metrics / uniqueItems
```
Added value: +true
```
addedInput schema / properties / output / additionalProperties
```
Added value: +false
```

changedInput schema / properties / output / description

Previous value: -"Optional output controls such as response format hints."New value: +"Optional response controls. v1 supports rows only."

addedInput schema / properties / output / properties

Added value: +{
+  "format": {
+    "default": "rows",
+    "enum": [
+      "rows"
+    ],
+    "type": "string"
+  },
+  "include_provenance": {
+    "default": false,
+    "type": "boolean"
+  }
+}

addedInput schema / properties / pack_id / minLength
```
Added value: +1
```

changedInput schema / properties / sort / anyOf

Previous value: -[
-  {
-    "type": "array"
-  },
-  {
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "direction": {
+        "enum": [
+          "asc",
+          "desc"
+        ],
+        "type": "string"
+      },
+      "field": {
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "field"
+    ],
+    "type": "object"
+  },
+  {
+    "items": {
+      "additionalProperties": false,
+      "properties": {
+        "direction": {
+          "enum": [
+            "asc",
+            "desc"
+          ],
+          "type": "string"
+        },
+        "field": {
+          "minLength": 1,
+          "type": "string"
+        }
+      },
+      "required": [
+        "field"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  }
+]

changedInput schema / properties / sort / description

Previous value: -"Optional sort instructions for row-returning queries."New value: +"Sort by a sortable field from get_pack; direction defaults to asc."

AddedSep 21, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/non-destructive/closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: parent administrative loc_ids expand to descendant rows at the pack's published grain, and disaster event rows carry stable event_id values for drill-down. No permission, rate-limit, or failure behavior is described, but that is a minor gap.

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?

Four front-loaded sentences with no filler; the core action and its inputs come first, then drill-down, hierarchy, and prerequisite notes. The final clause about 'geometry families' is slightly cryptic but not wasteful.

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?

For a 7-parameter tool with nested filter/sort objects and an output schema, the description covers the essential query model and prerequisites. Return-format details are correctly delegated to the output schema; only minor gaps remain around limit defaults and the output/request_id controls.

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 86%, so the baseline is 3; the description earns above that by explaining the hierarchy semantics of loc_id filters (a parent selects matching descendants) and clarifying that metrics must be exact published ids. It does not say much about sort, limit, output, or request_id, but those are already documented in 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?

States a specific verb and resource ('Retrieve rows from one selected published data pack') and enumerates the selection mechanisms (metrics, loc_id region filters, time/metric filters, sorting, row limit). The prerequisite on get_pack and the note about geometry families implicitly separate it from its catalog/pack siblings.

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?

'Call get_pack first' gives an explicit prerequisite, and 'geometry families use their focused next-step tools' routes a class of users away from this tool. It stops short of naming those alternative tools or stating when-not conditions for non-geometry cases, so it is clear context rather than full when/when-not guidance.

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.