Skip to main content
Glama
Sign In

Politics Feeds

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Fetch Feed

fetch_feed
Read-onlyIdempotent

Fetch and normalize any RSS / Atom / RDF feed by URL. CF-robust: fetches directly and falls back to a proxy if the source blocks the gateway. Use list_feeds first for curated sources.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "https://www.theguardian.com/politics/rss"
    },
    "name": "fetch_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFeed URL, e.g. "https://news.ycombinator.com/rss".
limitNoMax items (1-50, default 20).
queryNoKeyword filter over item title/summary.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "url": "https://www.theguardian.com/politics/rss"
+  },
+  {
+    "limit": 15,
+    "query": "senate",
+    "url": "https://feeds.politico.com/politico-news-feed.xml"
+  }
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, indicating a safe, non-destructive operation. The description adds valuable context like 'CF-robust: fetches directly and falls back to a proxy if the source blocks the gateway', disclosing fallback behavior 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?

Two sentences that efficiently convey purpose and usage guidance. No unnecessary words, and the key information is front-loaded.

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 fetch tool with 3 parameters and no output schema, the description covers purpose, usage guidance, and a key behavioral trait (fallback). It sufficiently differentiates from siblings in a list of 30+ tools. Could mention that it returns normalized feed items, but still complete enough.

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 input schema already documents all three parameters well. The description does not add new semantic information about parameters beyond what the schema provides, so a baseline score of 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?

The description clearly states it fetches and normalizes any RSS/Atom/RDF feed by URL. It distinguishes from the sibling 'list_feeds' by suggesting to use that for curated sources, making the purpose distinct.

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

Usage Guidelines5/5

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

Explicitly advises to use 'list_feeds' first for curated sources, providing a clear when-not-to-use scenario and suggesting an alternative tool. This helps an AI agent decide which tool to invoke.

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

All Politics Feeds toolsInspect
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