Skip to main content
Glama

Travel 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").

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Description goes beyond annotations by detailing fan-out logic, fallback from GDELT to GNews on errors, USPTO soft-fail, accepted input formats, and return structure (changes[], total_changes, citation URIs). No contradiction with readOnlyHint/idempotentHint annotations.

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 a single block of text that front-loads example queries and provides comprehensive details. It is informative but slightly verbose; could be tighter while retaining all information.

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?

Given the complexity of multiple data sources, fallback behavior, and no output schema, the description fully explains what the tool returns (changes grouped by source, total count, citation URIs) and handles edge cases (USPTO deactivation, GDELT/GNews fallback). No gaps.

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

Parameters5/5

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

Despite 100% schema coverage, description adds value with concrete examples (e.g., '7d', '30d', '1y'), best practice guidance ('Use 30d or 1m for typical monitoring'), and clarifies value accepts ticker or CIK.

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?

Description clearly states the tool provides a change feed for a company over a time window, fanned out to SEC, GDELT/GNews, and USPTO. It distinguishes from sibling tool entity_profile by specifying alternative use cases.

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?

Description provides explicit example queries and guidance on when to use entity_profile instead. However, it does not mention other related tools like fetch_feed or read_feed, missing some sibling differentiation.

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

All Travel 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.8/5.0
Disambiguation2/5

ask_pipeworx, ask_pipeworx_beta (explicitly identical right now), ask_pipeworx_grounded, and deep_research all answer natural-language data questions with subtly different trade-offs, requiring deep description reading to choose correctly. Six polymarket_* tools plus bet_research create heavy overlap in the prediction-market space, and scan_competitor_ai_presence is a thin wrapper over ai_visibility_check. Some clusters are clean (memory trio, subscription lifecycle, feed tools), but the query and market clusters have genuinely fuzzy boundaries.

Naming Consistency3/5

All names are snake_case, which helps, but the pattern is mixed: verb-first names (list_feeds, resolve_entity, validate_claim) coexist with noun-first names (entity_profile, polymarket_edges, recent_alerts) and product-specific variants (ask_pipeworx_beta, ask_pipeworx_grounded). Domain prefixes like polymarket_ and pipeworx_ provide some predictability, but there is no consistent verb_noun convention across the set.

Tool Count2/5

34 tools is well past the 25+ threshold for heavy, and it is egregious for a server whose stated purpose is 'Travel Feeds' — only three tools (list_feeds, read_feed, fetch_feed) relate to that domain. Even judged as a data-platform server, the count feels bloated with off-topic utilities like generate_llms_txt, scan_dependency, and the AI-visibility tools that belong elsewhere.

Completeness2/5

For the stated travel-feeds purpose, the surface is severely thin: you can list, read, and fetch feeds, but there is no cross-feed search, no aggregation, and the subscription system cannot even subscribe to travel-feed updates (only sec_8k, polymarket_edge, and fred_series). For the actual inferred domain (broad data research/prediction markets), coverage is extensive, but the inclusion of unrelated utilities and the server-name mismatch leave it incoherent and hard to reason about as a complete surface.

Resources