Skip to main content
Glama
Odds-API MCP Server

Odds-API MCP Server

Official

List live events

get_live_events
Read-onlyIdempotent

Retrieve live in-play sports events with current scores and match clocks, filtered by sport. Limit returned fields and results to keep responses small.

Instructions

List events in play now with scores and the match clock, optionally for one sport. Pass sport and fields to keep the response small.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_live_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
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. Changed3 schema fields changedv1.8.3
    • addedInput schema / properties / fields
      Added value: +{
      +  "description": "Optional comma-separated top-level fields to keep on each item (e.g. 'id,home,away,date,status'). Trims large responses.",
      +  "type": "string"
      +}
    • addedInput schema / properties / maxResults
      Added value: +{
      +  "description": "Optional cap on the number of items returned to you (applied after the API call).",
      +  "type": "number"
      +}
    • changedInput schema / properties / sport / description
      Previous value: -"Sport slug to filter live events (e.g., 'football')"New value: +"Sport slug from get_sports (e.g. 'football', 'basketball', 'tennis')"
  2. First observedv1.5.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds useful value by stating what comes back (scores and match clock) and by noting the payload can be trimmed, but says nothing about result volume, empty-state behavior, or how pruning affects the data.

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?

Two short sentences with the core purpose front-loaded and the optimization hint second. The second sentence largely duplicates the schema's own field guidance, which is the only slack in an otherwise tight definition.

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 usefully compensates by naming the returned data (scores, match clock). For a no-required-param, three-optional-param list tool with full annotation coverage, this is nearly sufficient, missing only any note about result volume or ordering.

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 three parameters are documented with examples and the fields/maxResults trimming mechanics are fully explained in the schema. The description only restates the trimming advice ('Pass sport and fields to keep the response small') and adds no semantics beyond it, making the baseline of 3 appropriate.

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?

The description gives a specific verb and resource ('List events in play now') plus the return payload ('scores and the match clock'), and the in-play qualifier implicitly separates it from get_events and search_events. It stops short of naming those siblings explicitly, so an agent must infer the boundary from the wording.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the tool is for currently live events, optionally narrowed by sport. There is no statement of when to prefer it over get_events, search_events, or get_event, and no exclusions or preconditions (such as needing a sport slug from get_sports) are spelled out in the description.

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