Skip to main content
Glama
Sign In

Transport Feeds

by io.github.pipeworx-io
OverviewDiscussionsAdmin

List Feeds

list_feeds
Read-onlyIdempotent

List the curated transport & mobility feeds (id, title, category, source). Optionally filter by category (automotive, transport) or keyword. Pass an id to read_feed.

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": {
      "category": "automotive"
    },
    "name": "list_feeds"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoKeyword to match in feed title/source/description.
categoryNoFilter by category: automotive, transport.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "category": "automotive"
+  },
+  {
+    "query": "electric vehicles"
+  }
+]
  2. 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 that the tool returns specific fields (id, title, category, source), which is useful context beyond the annotations. No contradictions.

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 consists of two short sentences with zero wasted words. It efficiently communicates purpose, features, and reference to a sibling tool.

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 list tool with no output schema, the description adequately covers what it returns and how to filter. It also directs to the sibling 'read_feed'. One minor omission is not mentioning any pagination or result limits, but given the annotations and simplicity, it is nearly complete.

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 coverage is 100%, so the baseline is 3. The description mentions filtering by category (with examples) and keyword, which matches the 'category' and 'query' parameters in the schema. No additional semantics 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 explicitly states the tool lists curated transport & mobility feeds and specifies the returned fields (id, title, category, source). It clearly distinguishes from the sibling tool 'read_feed' by directing the agent to use that for a specific feed.

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 provides clear context: it lists feeds with optional filters by category or keyword, and instructs to use 'read_feed' for a specific id. While it does not explicitly state when not to use this tool, the guidance is sufficient.

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