Skip to main content
Glama
Sign In

Transport 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://feeds.bloomberg.com/markets/automotive.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
    • changedInput schema / examples
      Previous value: -[
-  {
-    "url": "https://feeds.bloomberg.com/markets/automotive.rss"
-  },
-  {
-    "limit": 15,
-    "query": "autonomous",
-    "url": "https://feeds.reuters.com/news/transportIndustry"
-  }
-]New value: +[
+  {
+    "url": "https://feeds.bloomberg.com/markets/automotive.rss"
+  },
+  {
+    "limit": 15,
+    "url": "https://www.truckingdive.com/feeds/news/"
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "url": "https://feeds.bloomberg.com/markets/automotive.rss"
+  },
+  {
+    "limit": 15,
+    "query": "autonomous",
+    "url": "https://feeds.reuters.com/news/transportIndustry"
+  }
+]
  3. First observed

TDQS

A4.2/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. The description adds value by explaining normalization and the proxy fallback behavior, going beyond the structured 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?

The description is two sentences long, front-loaded with the core action, and contains no extraneous information. Every sentence provides essential context.

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 lack of output schema, the description could be more explicit about the return format (e.g., list of items). However, stating 'normalize' implies a structured output, and the tool's read-only nature is clear from annotations.

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 schema already documents all parameters. The description does not add extra meaning for parameters beyond what the schema provides, maintaining the baseline score.

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 verb 'Fetch and normalize' and the resource 'any RSS / Atom / RDF feed by URL'. It distinguishes from sibling tools like 'list_feeds' by specifying it works with arbitrary URLs and includes normalization.

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 advises to 'Use list_feeds first for curated sources,' providing clear context for when to use this tool versus an alternative. It also mentions the proxy fallback for robustness, though does not explicitly list when not to use.

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

All Transport 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