Skip to main content
Glama

Odds Api

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.9/5.0
Behavior5/5

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

Annotations already mark it as read-only, idempotent, and non-destructive. The description adds substantial behavioral detail: fans out to multiple sources (SEC, GDELT/GNews, USPTO), describes fallback logic, mentions API sunset, and outlines the return structure. 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.

Conciseness4/5

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

The description is well-structured with user query examples first, then behavioral details, then sibling differentiation. Every sentence adds value, though it could be slightly more concise given the detail. Still excellent.

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 exists, so the description fully compensates by stating the return format (changes[] grouped by source, total_changes count, citation URIs). It also addresses edge cases (fallback, sunset) and provides complete usage context.

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?

Schema coverage is 100%, so baseline is 3. The description adds significant value beyond schema: explains since format with examples (ISO date and relative shorthand), clarifies value can be ticker or CIK, and notes type is limited to 'company'. This enriches understanding for proper invocation.

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 tool's purpose: a change feed for a company in a specified window, with concrete examples of user queries. It distinguishes itself from the sibling tool entity_profile by specifying when to use that instead.

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?

Explicitly provides when-to-use guidance, including alternative tool (entity_profile for static profile). Explains input formats for since parameter with examples and fallback behavior between GDELT and GNews.

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

All Odds Api 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
Disambiguation3/5

Most tools have distinct scopes, and the long cross-referencing descriptions help a lot. However, ask_pipeworx_beta is currently an exact duplicate of ask_pipeworx by the server's own description, and the polymarket_* family plus ask_pipeworx/ask_pipeworx_grounded/deep_research have overlapping boundaries that could mislead an agent.

Naming Consistency4/5

The vast majority follow a clear verb_noun snake_case pattern like get_odds, list_sports, resolve_entity, and subscribe. A few exceptions such as odds_api_quota, pipeworx_feedback, polymarket_arbitrage, and recall break the pattern slightly, but the overall convention is predictable.

Tool Count2/5

37 tools is well past the 25+ threshold and feels bloated for a server named 'Odds Api'. Many tools are meta-platform utilities — memory, feedback, trending, dependency scanning, llms.txt generation — that have no obvious connection to an odds API and make the surface hard to navigate.

Completeness4/5

The odds domain is well covered: list_sports, get_events, get_odds, get_event_odds, get_scores, quota tracking, and subscriptions form a coherent read/monitor workflow. Minor gaps exist — no historical odds or a single-event detail endpoint — but agents can complete core odds research and monitoring tasks without dead ends.

Resources