Skip to main content
Glama

Transport Feeds

by io.github.pipeworx-io

Recent Changes

recent_changes
Read-onlyIdempotent

"What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple" — change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings since since), GDELT→GNews fallback (news mentions in window — GDELT preferred, GNews when rate-limited or 5xx), USPTO (patents granted; PatentsView API sunset May 2025 so this soft-fails until reactivated). since accepts ISO date ("2026-04-01") or relative shorthand ("7d", "30d", "3m", "1y"). Returns structured changes[] grouped by source + total_changes count + pipeworx:// citation URIs. Use entity_profile instead when you want the static profile (filings + fundamentals + LEI + patents) regardless of window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesEntity type. Only "company" supported today.
sinceYesWindow start — ISO date ("2026-04-01") or relative ("7d", "30d", "3m", "1y"). Use "30d" or "1m" for typical monitoring.
valueYesTicker (e.g., "AAPL") or zero-padded CIK (e.g., "0000320193").

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare it read-only and idempotent. Description adds multi-source fan-out, GDELT→GNews fallback, and patents soft-failure due to API sunset.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is informative but slightly long; could be tightened. However, it is front-loaded with example use cases and structured explanation of sources.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, but description mentions return structure (changes grouped by source, total_changes, citation URIs). All 3 params are well-defined. Sufficient for agent to understand what to expect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%. Description adds by explaining `since` accepts ISO or relative shorthand (e.g., '30d') and recommends '30d' or '1m'. Also clarifies `type` enum only supports 'company'.

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 provides a change feed for a company, listing SEC filings, news, and patents in one call. It starts with example queries and distinguishes from sibling tool entity_profile.

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?

Provides explicit when-to-use examples and when-not-to (use entity_profile for static profiles). Also explains fallback behavior and soft-fails.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation2/5

There is substantial overlap among the many question-answering tools (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, validate_claim, compare_entities, entity_profile, recent_changes) and the prediction-market tools (polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread). While each has nuanced differences, agents will struggle to select the right one, especially with several 'ask_pipeworx' variants that behave nearly identically.

Naming Consistency3/5

Most tool names use snake_case, but patterns vary widely: some are verb_noun (list_feeds, read_feed, subscribe, unsubscribe, remember), others are noun_phrases (polymarket_arbitrage, pipeworx_trending, entity_profile), and a few like 'ask_pipeworx' and 'bet_research' don't follow a consistent structure. The mixed conventions make prediction of new tool names difficult.

Tool Count2/5

With 34 tools, this is far too many for a server named 'Transport Feeds'. The majority of tools are unrelated to transport feeds, covering generic data research, prediction markets, and memory utilities. The count overwhelms any focused purpose and would require extensive discovery to navigate.

Completeness3/5

For the actual data-research and prediction-market functions, the surface is quite complete—covering lookups, comparisons, grounded verification, arbitrage scans, fill risk, trending, and subscriptions. However, for the declared domain (transport feeds), there are only two feed-specific tools (list_feeds, read_feed) with no write/update/delete operations, leaving obvious gaps.

Resources