Mellow Mountain Radio

Local News Headlines

get_local_news_headlines

Read-onlyIdempotent

Returns the latest Sedona and Verde Valley local news headlines. Pulls live from the Sedona Red Rock News and Verde Independent RSS feeds. Covers local government, arts, community events, real estate, and Verde Valley news.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Max headlines to return per source (default 8)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`feeds`	Yes
`errors`	No
`updated`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedJul 25, 2026
- removedOutput schema / properties / errors / items / type
```
Removed value: -"string"
```
- changedOutput schema / properties / feeds / items / properties / items / items / additionalProperties
```
Previous value: -falseNew value: +true
```
- changedOutput schema / properties / feeds / items / properties / items / items / properties / link / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / feeds / items / properties / items / items / properties / published / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / feeds / items / properties / items / items / properties / summary / type
```
Previous value: -"string"New value: +[
+  "string",
+  "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": {
+    "errors": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "feeds": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "count": {
+            "type": "number"
+          },
+          "items": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "link": {
+                  "type": "string"
+                },
+                "published": {
+                  "type": "string"
+                },
+                "summary": {
+                  "type": "string"
+                },
+                "title": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "title"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "source": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "source",
+          "count",
+          "items"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "updated": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "updated",
+    "feeds"
+  ],
+  "type": "object"
+}

First observedJul 24, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds that data is pulled live from RSS feeds, providing source and real-time context beyond annotations.

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 redundancy, front-loaded with the core purpose. Every sentence adds value and no unnecessary words.

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 simple parameter, the description covers purpose and sources. It could mention output format briefly, but is sufficient for a straightforward tool.

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 description coverage is 100%, so the parameter 'limit' is fully documented in the schema. The description adds no additional parameter-level detail 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?

The description clearly states the tool returns local news headlines from specific sources (Sedona Red Rock News, Verde Independent) covering defined topics. It distinguishes from sibling tools like get_events or get_nws_alerts by specifying geographic and content focus.

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?

The description implies usage for obtaining Sedona and Verde Valley local news. It does not explicitly state when not to use or mention alternatives, but the narrow scope makes the context clear.

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?