Skip to main content
Glama

Odds Api

by io.github.pipeworx-io

Get Odds

get_odds
Read-onlyIdempotent

Current odds for upcoming + live events in a league. Each market type costs 1 quota credit per region per call — pick markets carefully.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
marketsNoh2h | spreads | totals | outrights — comma-sep (default h2h)
regionsNous | uk | eu | au — comma-sep (default us)
event_idsNoRestrict to specific event IDs (comma-sep)
sport_keyYesSport key from list_sports, e.g. "americanfootball_nfl"
bookmakersNoComma-sep bookmaker keys (e.g. "draftkings,fanduel") to restrict
date_formatNoiso (default) | unix
odds_formatNoamerican (default) | decimal

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesNumber of items returned.
itemsYes

Schema Changelog

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

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "markets": "h2h",
+    "regions": "us",
+    "sport_key": "americanfootball_nfl"
+  },
+  {
+    "bookmakers": "draftkings,fanduel",
+    "markets": "spreads,totals",
+    "odds_format": "decimal",
+    "regions": "us,uk",
+    "sport_key": "basketball_nba"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of items returned.",
+      "type": "integer"
+    },
+    "items": {
+      "items": {
+        "properties": {
+          "away_team": {
+            "description": "Away team name",
+            "type": "string"
+          },
+          "bookmakers": {
+            "items": {
+              "properties": {
+                "key": {
+                  "description": "Bookmaker key",
+                  "type": "string"
+                },
+                "last_update": {
+                  "description": "Last odds update time",
+                  "type": "string"
+                },
+                "markets": {
+                  "items": {
+                    "properties": {
+                      "key": {
+                        "description": "Market type (h2h, spreads, totals)",
+                        "type": "string"
+                      },
+                      "last_update": {
+                        "description": "Market last update time",
+                        "type": "string"
+                      },
+                      "outcomes": {
+                        "items": {
+                          "properties": {
+                            "name": {
+                              "description": "Outcome name (team/option)",
+                              "type": "string"
+                            },
+                            "point": {
+                              "description": "Spread/total point (if applicable)",
+                              "type": "number"
+                            },
+                            "price": {
+                              "description": "Odds (american or decimal)",
+                              "type": "number"
+                            }
+                          },
+                          "type": "object"
+                        },
+                        "type": "array"
+                      }
+                    },
+                    "type": "object"
+                  },
+                  "type": "array"
+                },
+                "title": {
+                  "description": "Bookmaker name",
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "commence_time": {
+            "description": "Event start time (ISO 8601 or unix)",
+            "type": "string"
+          },
+          "home_team": {
+            "description": "Home team name",
+            "type": "string"
+          },
+          "id": {
+            "description": "Event ID",
+            "type": "string"
+          },
+          "sport_key": {
+            "description": "Sport key",
+            "type": "string"
+          },
+          "sport_title": {
+            "description": "Sport title",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items",
+    "count"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare read-only, idempotent, non-destructive behavior. Description adds the crucial behavioral detail of quota credit consumption, which is beyond annotations. No contradiction.

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?

Two-sentence description: first sentence succinctly states purpose, second delivers critical usage constraint. No unnecessary words, highly efficient.

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?

Covers core functionality and cost implications. With output schema present, return structure is documented. Could briefly mention required sport_key, but it's implied by 'in a league'.

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%, so baseline is 3. The description adds value by linking markets and regions to credit cost, aiding parameter selection. Each parameter is well-defined in 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 clearly states the tool retrieves current odds for upcoming and live events in a league, using a specific verb and resource. It distinguishes itself from sibling 'get_event_odds' which focuses on individual events.

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?

Provides explicit guidance on quota credit cost per market/region, advising careful selection. Lacks explicit comparison to alternative tools or when-not-to-use conditions, but the cost note is practical.

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

Several tool clusters have unclear boundaries: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route to the same 5,724 tools with only subtle behavioral differences, and bet_research, polymarket_edges, polymarket_arbitrage, and polymarket_kalshi_spread heavily overlap around prediction-market opportunity discovery. entity_profile, compare_entities, and recent_changes also fan out across the same SEC/news/patent sources, making selection ambiguous for agents.

Naming Consistency2/5

Naming mixes multiple conventions: snake_case verb_noun for odds tools (get_events, list_sports), vendor-prefixed clusters (ask_pipeworx_*, pipeworx_*, polymarket_*), and a few reversed noun-verb names like bet_research. CamelCase is used in ai_visibility_check and generate_llms_txt adds another style. Only the polymarket_* and pipeworx_* families are internally consistent, but the overall pattern is chaotic.

Tool Count2/5

37 tools is well beyond the typical well-scoped server, and the count feels inflated by unrelated meta-tools (suggest_questions, discover_tools, pipeworx_feedback, pipeworx_trending, generate_llms_txt, scan_dependency, remember/recall/forget) that have nothing to do with the server's stated 'Odds Api' purpose. The actual odds surface is only ~5 tools, so the vast majority of the catalog is off-scope padding.

Completeness3/5

The core odds domain is well covered: list_sports, get_events, get_odds, get_event_odds, and get_scores form a coherent lifecycle, plus quota introspection. However, for the server's actual broad-research scope there are noticeable gaps (e.g., no direct single-filing fetch tool despite heavy SEC coverage, a lone npm-dependency tool with no surrounding ecosystem, and no historical/past-odds endpoint), and the heterogeneous domains make completeness uneven.

Resources