Mellow Mountain Radio

Emergency Alerts

get_emergency_alerts

Read-onlyIdempotent

Returns active Emergency Alert System (EAS) alerts for the Sedona area — Yavapai and Coconino counties. Covers weather emergencies, evacuation orders, Amber Alerts, and all FEMA IPAWS-distributed alerts. Data is live from the National Weather Service public API.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`severity`	No	Filter to alerts at or above this severity level (Extreme > Severe > Moderate > Minor)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`alerts`	Yes
`updated`	Yes
`counties`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "alerts": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "areas": {
+            "type": "string"
+          },
+          "certainty": {
+            "type": "string"
+          },
+          "description": {
+            "type": "string"
+          },
+          "effective": {
+            "type": "string"
+          },
+          "event": {
+            "type": "string"
+          },
+          "expires": {
+            "type": "string"
+          },
+          "headline": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "instruction": {
+            "type": "string"
+          },
+          "sender": {
+            "type": "string"
+          },
+          "severity": {
+            "type": "string"
+          },
+          "urgency": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "event"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "count": {
+      "type": "number"
+    },
+    "counties": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "updated": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "updated",
+    "counties",
+    "count",
+    "alerts"
+  ],
+  "type": "object"
+}

First observedJul 24, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare the tool as read-only, idempotent, and non-destructive. Description adds that data is live from the NWS public API, providing some extra behavioral context but not delving into performance or edge cases.

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?

Three sentences, no wasted words. The core information is front-loaded, making it easy for an agent to quickly grasp the tool's purpose.

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 presence of an output schema and comprehensive annotations, the description adequately covers scope, content types, and data source. Minor missing detail on update frequency, but not critical for tool selection.

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 coverage is 100% and the single 'severity' parameter is well-described in the schema. The tool description does not add further parameter semantics beyond what the schema provides.

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 states the tool returns active Emergency Alert System alerts for a specific geographic area (Sedona, Yavapai/Coconino counties). It lists alert types and mentions the live data source, effectively distinguishing it from siblings like get_nws_alerts.

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?

Usage context is implied (for Sedona area emergency alerts), but no explicit guidance on when to use this tool versus alternatives, nor any conditions for not using it.

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

All Mellow Mountain Radio 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.

Resources

Need Help?