Skip to main content
Glama

SportStatsAPI

Get live matches

get_live_matches
Read-only

Matches in play right now, with score and minute or period, and the TV channels showing them where known.

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": {
      "sport": "<sport>"
    },
    "name": "get_live_matches"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNolanguage of team, league and country names: de, es, it or fr (default English)
sportYessport (see list_sports)
league_idNoonly this league

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / league_id / type
      Previous value: -"integer"New value: +[
      +  "integer",
      +  "string"
      +]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the returned payload (score, minute/period, TV channels) and hedging on availability with 'where known', which is consistent with idempotentHint=false for volatile live data. No rate-limit or refresh-cadence info, but nothing is contradicted.

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?

A single front-loaded sentence with zero filler: the core scope comes first and the payload details follow. Every clause earns its place.

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 takes on the job of sketching the return values, and it does so adequately for a simple filtered-read tool with fully documented parameters. It stops short of noting coverage limits (which sports have live data) or behavior when nothing is in play, but nothing essential to a correct call is missing.

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 coverage is 100%, so sport, league_id and lang are already documented in the schema, including the language code list and the pointer to list_sports. The description adds no further meaning to any of the three parameters, so the baseline 3 applies.

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 resource with a clear temporal scope: matches 'in play right now', plus what each result carries (score, minute or period, TV channels). This implicitly separates it from the date-oriented get_matches sibling, though it never names an alternative explicitly.

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 implied by 'right now' — an agent can infer this is the live-only query rather than a historical or scheduled fixture lookup. There is no explicit when-not guidance, no mention of prerequisites, and no named alternative for fetching non-live matches.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources