Skip to main content
Glama

Usgs Volcano

by io.github.pipeworx-io
OverviewDiscussionsAdmin

List Notices

list_notices
Read-onlyIdempotent

Recent USGS volcano notices and reports — observatory updates, VAN (Volcano Activity Notice) and VONA (Volcano Observatory Notice for Aviation) text. Filter by volcano slug.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoCap notices returned (default 50)
volcano_slugNoUSGS volcano slug (e.g., "kilauea", "shishaldin"). Optional — omit for all recent.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesNumber of notices returned
noticesYesList of volcano notices and alerts
volcano_slugYesFiltered volcano slug if provided, otherwise null

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {},
+  {
+    "limit": 10,
+    "volcano_slug": "kilauea"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of notices returned",
+      "type": "number"
+    },
+    "notices": {
+      "description": "List of volcano notices and alerts",
+      "items": {
+        "properties": {
+          "alert_level": {
+            "description": "Alert level at time of notice",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "color_code": {
+            "description": "Color code at time of notice",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Notice ID",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "message": {
+            "description": "Full notice message text",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "observatory": {
+            "description": "Observatory code",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "sent_utc": {
+            "description": "Timestamp when notice was sent (UTC)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "slug": {
+            "description": "Volcano slug",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "summary": {
+            "description": "Brief summary of the notice",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "type": {
+            "description": "Message type (VAN, VONA, etc.)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "url": {
+            "description": "URL to full notice",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "volcano": {
+            "description": "Volcano name",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "volcano_slug": {
+      "description": "Filtered volcano slug if provided, otherwise null",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "volcano_slug",
+    "count",
+    "notices"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already thoroughly describe safety (readOnlyHint, idempotentHint, etc.). Description adds temporal context ('recent') and content specifics (observatory updates, VAN, VONA) which go slightly beyond annotations, but lacks details on data freshness, limits, or response format.

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?

Description is a single, well-structured sentence that front-loads key purpose and capabilities. No unnecessary words or repetition.

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 simple list tool with optional filters, full schema coverage, and an output schema (implied), the description is sufficient. It clearly explains what notices are retrieved. Could slightly improve by noting that output is textual or structured, but not required.

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 has 100% description coverage for both parameters (limit, volcano_slug). Description mentions filtering by volcano slug but adds no new meaning beyond what schema provides. Baseline 3 is appropriate.

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?

Description clearly identifies the tool as listing recent USGS volcano notices and reports, specifying types (VAN, VONA) and filter capability by volcano slug. This distinguishes it from sibling like 'list_volcanoes' and other query tools.

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

Usage Guidelines3/5

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

Description implies usage for retrieving volcano notices, but does not explicitly state when to use this tool versus alternatives (e.g., 'recent_alerts'), nor does it provide exclusions or context for selection. Usage is inferred but not guided.

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

All Usgs Volcano toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources