Skip to main content
Glama
Sign In
Odds-API MCP Server

Odds-API MCP Server

Official
by odds-api-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search historical events

search_historical_events
Read-onlyIdempotent

Find finished sports events by team name across all leagues or a single sport within a 31-day date range, returning event IDs for historical odds lookup.

Instructions

Find finished events by team name across all leagues, optionally for one sport. Date span max 31 days (default: the last 31 days). Returns up to 100 events, newest first. Use the ids with get_historical_odds.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_historical_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd date in RFC3339 format, at most 31 days after from
fromNoStart date in RFC3339 format
queryYesTeam name fragment, minimum 3 characters
sportNoSport slug from get_sports (e.g. 'football', 'basketball', 'tennis')
fieldsNoOptional comma-separated top-level fields to keep on each item (e.g. 'id,home,away,date,status'). Trims large responses.
maxResultsNoOptional cap on the number of items returned to you (applied after the API call).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.8.3

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds genuinely new behavior: the default 31-day lookback, the 31-day hard span limit, and a result cap of 100 ordered newest-first — details absent from the annotations.

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?

Four short sentences, each carrying distinct information: purpose, constraint, return shape, next step. Scope is front-loaded and nothing is repeated from the schema or annotations.

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?

With no output schema, the description supplies the essentials an agent needs: result count, ordering, and how to chain into get_historical_odds. It leaves open whether results beyond 100 are reachable (paging) and how team-name matching behaves, minor gaps for a read-only search tool.

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 the baseline is 3, and the description earns above that by documenting default behavior the schema omits (from/to default to the last 31 days) and the 100-item ceiling that contextualizes maxResults. It does not explain the interaction between maxResults and the API-side 100 cap, leaving one ambiguity.

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 with scope: 'Find finished events by team name across all leagues, optionally for one sport.' The word 'finished' implicitly separates it from live/upcoming search siblings, but no sibling (e.g. search_events, get_historical_events) is named, so the agent must infer the boundary.

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?

Gives concrete operating context: default window is the last 31 days, max span 31 days, and a downstream step ('Use the ids with get_historical_odds'). It does not state when to prefer get_historical_events or search_events instead, so the routing decision is only implied.

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