Skip to main content
Glama

Sports Feeds

by io.github.pipeworx-io

Entity Profile

entity_profile
Read-onlyIdempotent

"Tell me about X" / "research Acme" / "brief me on Tesla" / "what does Apple do" / "company profile for Microsoft" / "give me the rundown on NVDA" / "everything you know about $TICKER" — full cross-source profile of a US public company in ONE parallel call. ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view. Fans out across SEC EDGAR, XBRL, USPTO patents, federal contracts (USAspending), FDA-licensed biologics (Purple Book), H-1B hiring (DOL LCA), news and GLEIF, and returns: cik + company_name (+ resolved_from/resolved_to when value was a name); recent_filings (up to 5 with pipeworx://edgar/company/{cik}/filings/{accession} URIs); fundamentals (LATEST 10-K Revenues + NetIncomeLoss + Cash, sorted period_end DESC); patents (USPTO PatentsView API sunset May 2025 — soft-fails until reactivated); federal_contracts (USAspending awards where the company is the recipient); fda_products (FDA-licensed biologics — vaccines, cell/gene therapies — from the Purple Book; a company with only small-molecule/generic drugs will show none here, that is expected, not a failure); hiring (H-1B sponsorship volume + salary range from DOL LCA filings); recent news mentions via GDELT→GNews fallback; LEI via GLEIF. sources_used / sources_failed say which of these actually returned data for THIS company — an empty section is a real "no data", not a bug. Pass a ticker ("AAPL"), zero-padded CIK ("0000320193"), OR a company name ("Moderna") — names now resolve via SEC EDGAR's company-name match; a private company (no CIK/ticker) returns resolved:false with an explicit notes line, not a bare failure. type accepts "company" or "ticker" interchangeably — both take the same value shapes above.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYes"company" or "ticker" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon.
valueYesTicker (e.g., "AAPL"), zero-padded CIK (e.g., "0000320193"), or company name (e.g., "Moderna") — names resolve via SEC EDGAR company-name match.

TDQS

A4.8/5.0
Behavior5/5

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

Beyond readOnly/idempotent annotations, the description discloses behavioral specifics: parallel fan-out across SEC EDGAR/XBRL/USPTO/news/GLEIF, patents API sunset with soft-fail, GDELT→GNews fallback, and unsupported-name behavior. No contradiction with 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?

The description is long, but every segment carries distinct information—triggers, preference rule, source list, return fields, limitations. It is front-loaded with query examples; only minor redundancy with the schema makes it a 4 rather than 5.

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 no output schema, the description enumerates exact return fields (cik, company_name, recent_filings with URIs, fundamentals, patents, news, LEI), plus failure/fallback behavior and input constraints. This is enough for an agent to select and use the tool correctly.

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?

The schema already covers both params 100%; the description reinforces with ticker/CIK examples, 'zero-padded' formatting, and repeats the resolve_entity fallback for names. This adds practical usage nuance but is largely complementary to the schema.

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 opens with concrete user phrasing ('Tell me about X', 'research Acme') and defines the tool as a 'full cross-source profile of a US public company in ONE parallel call.' It distinguishes itself from sibling single-purpose lookups and explicitly positions itself as the holistic alternative.

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?

It explicitly states 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view,' and gives a clear exclusion: names are not supported — use resolve_entity first. This tells the agent exactly when to invoke and when to route elsewhere.

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

All Sports 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.6/5.0
Disambiguation2/5

Several tools have heavily overlapping purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded differ only in mode, and the polymarket_* cluster (polymarket_edges, polymarket_edge_tracker, polymarket_arbitrage, polymarket_fill_risk, polymarket_kalshi_spread) all target prediction-market analysis with fuzzy boundaries. The presence of ai_visibility_check and scan_competitor_ai_presence, plus discover_tools and suggest_questions, adds further ambiguity about which tool to select first.

Naming Consistency3/5

Names are all snake_case but follow mixed conventions: verb_noun (list_feeds, read_feed, fetch_feed, validate_claim) coexists with noun_phrase (entity_profile, recent_changes, polymarket_edges) and prefix-grouped names (ask_pipeworx*, polymarket_*). While subgroups are internally consistent, the overall set lacks a unified pattern, though it remains readable.

Tool Count2/5

34 tools is well above the 25+ threshold for too many, and the count is especially inappropriate for a server named 'Sports Feeds' — most tools are generic data-research or meta-tools (subscriptions, memory, feedback, discovery) unrelated to sports feeds. The bloat suggests the server is actually a broad Pipeworx gateway, not a focused sports feeder.

Completeness2/5

For a sports-feeds server, only list_feeds, read_feed, and fetch_feed address the core domain, and there is no feed search, categorization beyond a simple list, or sports-specific analytics. While the general research surface (SEC, FDA, economics, prediction markets) is fairly comprehensive, it is misaligned with the stated server purpose, leaving the actual sports-feed functionality thin and with obvious gaps.

Resources