Mellow Mountain Radio

Fire Restrictions

get_fire_restrictions

Read-onlyIdempotent

Returns current fire restriction level and fire danger rating for the Sedona / Coconino National Forest area. Includes any active Stage 1 or Stage 2 restrictions and Sedona-area alerts.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`notes`	Yes
`stage`	Yes
`agency`	Yes
`danger`	Yes
`source`	Yes
`updated`	Yes
`sedona_alerts`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedJul 25, 2026
- addedOutput schema / properties / sedona_alerts / items / additionalProperties
```
Added value: +false
```
- addedOutput schema / properties / sedona_alerts / items / properties
```
Added value: +{
+  "text": {
+    "type": "string"
+  },
+  "url": {
+    "type": "string"
+  }
+}
```
- addedOutput schema / properties / sedona_alerts / items / required
```
Added value: +[
+  "text",
+  "url"
+]
```
- changedOutput schema / properties / sedona_alerts / items / type
```
Previous value: -"string"New value: +"object"
```
- changedOutput schema / properties / stage / type
```
Previous value: -[
-  "string",
-  "null"
-]New value: +[
+  "number",
+  "null"
+]
```

Changed1 schema field changedJul 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "agency": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "danger": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "notes": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "sedona_alerts": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "source": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "stage": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "updated": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "updated",
+    "agency",
+    "source",
+    "stage",
+    "danger",
+    "sedona_alerts",
+    "notes"
+  ],
+  "type": "object"
+}

First observedJul 24, 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=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful behavioral context: the tool returns restriction levels, danger rating, and active alerts. It does not contradict annotations and provides specificity beyond them.

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?

The description is a single, concise sentence (20 words) that front-loads the key information: what it returns and the location. Every word is necessary, no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has no parameters, rich annotations, and an output schema (not shown), the description is complete. It covers the returned data (restriction level, danger rating, alerts), the area, and the scope (Stage 1/2, Sedona-area). No additional context is needed for an agent to use it correctly.

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?

The input schema has zero parameters, and schema description coverage is 100%. With no parameters, the description does not need to add parameter information. Per rubric, 0 parameters earns a baseline of 4.

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 returns 'current fire restriction level and fire danger rating' for a specific area, distinguishing it from sibling tools like get_wildfire_perimeters (which likely provides fire perimeters) and get_emergency_alerts (broader alerts). The verb 'returns' and the resource 'fire restrictions' are specific and unambiguous.

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?

The description implies usage when needing fire restriction data for the Sedona/Coconino National Forest area, but gives no explicit guidance on when not to use it or alternatives. Sibling tools like get_wildfire_perimeters or get_emergency_alerts could be referenced, but are not.

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?