Skip to main content
Glama
Sign In

Politics Feeds

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Read Feed

read_feed
Read-onlyIdempotent

Read a curated politics & policy feed by its id (from list_feeds). Returns normalized items (title, link, published, summary). Optionally filter items by keyword.

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": {
      "feed": "the-bulwark"
    },
    "name": "read_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
feedYesCurated feed id (from list_feeds).
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
    • changedInput schema / examples
      Previous value: -[
-  {
-    "feed": "bbc-politics"
-  },
-  {
-    "feed": "cnn-politics",
-    "limit": 10,
-    "query": "congress"
-  }
-]New value: +[
+  {
+    "feed": "the-bulwark"
+  },
+  {
+    "feed": "rollcall",
+    "limit": 10,
+    "query": "congress"
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "feed": "bbc-politics"
+  },
+  {
+    "feed": "cnn-politics",
+    "limit": 10,
+    "query": "congress"
+  }
+]
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuine context beyond the annotations: it names the returned fields (title, link, published, summary) and the optional keyword filtering, which matters because there is no output schema. It omits ordering, pagination and unknown-id behavior.

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 tight sentences with the action and required id source front-loaded, then return shape, then the optional filter. No filler.

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?

With no output schema, the description usefully compensates by enumerating return fields, and all parameters are covered. The remaining gap is the unresolved overlap with the sibling fetch_feed and absence of ordering/pagination/error behavior.

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 all three parameters (feed, limit, query) are already documented in the schema. The description reinforces feed provenance and the query filter but never mentions limit, adding little beyond the structured fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Read a curated politics & policy feed by its id') and points to list_feeds as the id source. It does not distinguish itself from the sibling fetch_feed, so an agent cannot tell from the description alone which of the two feed-reading tools applies.

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?

It implies the prerequisite (id comes from list_feeds) and mentions an optional keyword filter, but gives no when-to-use vs when-not guidance and never addresses the fetch_feed sibling or error cases for an unknown feed id.

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