Skip to main content
Glama
odds-api-io

Odds-API MCP Server

Official
by odds-api-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_updated_odds

Fetch odds updated since a Unix timestamp for a bookmaker and sport, limited to named markets. The timestamp must be at most 90 seconds old. Use for efficient polling.

Instructions

Get odds updated since a Unix timestamp for a bookmaker and sport, limited to the markets you name. The timestamp must be at most 90 seconds old. Useful for efficient polling.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sinceYesUnix timestamp in seconds, at most 90 seconds old
sportYesSport slug (e.g., 'football')
marketsYesComma-separated market names, max 20 (e.g., 'ML,Spread,Totals'). Required by the API. Use get_markets for the exact names a sport serves.
bookmakerYesBookmaker name (e.g., 'Bet365')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.6.0
    • addedInput schema / properties / markets
      Added value: +{
+  "description": "Comma-separated market names, max 20 (e.g., 'ML,Spread,Totals'). Required by the API. Use get_markets for the exact names a sport serves.",
+  "type": "string"
+}
    • changedInput schema / properties / since / description
      Previous value: -"Unix timestamp (must be within the last 60 seconds)"New value: +"Unix timestamp in seconds, at most 90 seconds old"
    • changedInput schema / required
      Previous value: -[
-  "since",
-  "bookmaker",
-  "sport"
-]New value: +[
+  "since",
+  "bookmaker",
+  "sport",
+  "markets"
+]
  2. First observedv1.5.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose a real constraint: the timestamp must be at most 90 seconds old, which implies a hard polling window. It does not cover auth requirements, rate limits beyond that window, what happens when the window is violated, or what the response contains.

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?

Three short sentences, front-loaded with the operation and scope, then the constraint, then the use case. Minor redundancy in restating the 90-second limit that the schema already carries, but nothing is padded.

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

Completeness3/5

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

No output schema and no annotations, so the description should say more about the returned odds shape and the failure mode when 'since' is stale. It adequately covers the required inputs and the polling intent, but leaves the response contract unspecified.

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

Parameters3/5

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

Schema description coverage is 100%, so all four parameters are already documented, including the market limit and the pointer to get_markets. The description adds only the 'limited to the markets you name' scoping and restates the 90-second rule, so baseline 3 is correct.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get odds updated since a Unix timestamp') with the scoping axes (bookmaker, sport, markets), which implicitly separates it from the snapshot-oriented get_odds sibling. It never names an alternative explicitly, so an agent must infer the boundary from 'updated since' alone.

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?

The line 'Useful for efficient polling' gives a clear use context, and the 90-second freshness rule tells the agent when this call is valid. It does not state when NOT to use it (e.g., for a full snapshot use get_odds) or name a fallback when the timestamp is too old.

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

Deploy Server

Other Tools