Skip to main content
Glama

SportStatsAPI

Get matches

get_matches
Read-only

Matches (fixtures and results) by day or date range, optionally of one league, or one team's matches in every competition (team_id; without status or dates its latest results, then live, then next matches; with status scheduled only the next ones, with finished only the latest results). Without a date or team: today (UTC). Where known: TV channels by country (where to watch) and a highlights video link.

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_matches"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoday YYYY-MM-DD (UTC); without date, date_from, date_to, team_id or league_id: today only (UTC)
gameNoesports: cs2, dota2, lol or valorant
langNolanguage of team, league and country names: de, es, it or fr (default English)
limitNomax matches (default 20, max 100)
sportYessport (see list_sports)
offsetNoskip this many matches (paging)
statusNoscheduled, finished or live, or a status as the API reports it, e.g. FT or NS; with team_id finished lists the latest first; with team_id and no status or date: latest results then next matches
date_toNolast day YYYY-MM-DD of a range
team_idNoonly this team's matches in every competition (team code (or number) from find_teams; not tennis); without a date all of them
date_fromNofirst day YYYY-MM-DD of a range
league_idNoleague code (or number) from find_leagues
league_nameNoexact league name, picks one division where several share a league id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"day YYYY-MM-DD (UTC)"New value: +"day YYYY-MM-DD (UTC); without date, date_from, date_to, team_id or league_id: today only (UTC)"
  2. Changed2 schema fields changed
    • changedInput schema / properties / league_id / description
      Previous value: -"league id from find_leagues"New value: +"league code (or number) from find_leagues"
    • changedInput schema / properties / team_id / description
      Previous value: -"only this team's matches in every competition (team id from find_teams; not tennis); without a date all of them"New value: +"only this team's matches in every competition (team code (or number) from find_teams; not tennis); without a date all of them"
  3. Changed2 schema fields changed
    • changedInput schema / properties / league_id / type
      Previous value: -"integer"New value: +[
      +  "integer",
      +  "string"
      +]
    • changedInput schema / properties / team_id / type
      Previous value: -"integer"New value: +[
      +  "integer",
      +  "string"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / status / description
      Previous value: -"scheduled, finished or live, or a status as the API reports it, e.g. FT or NS; with team_id finished lists the latest first"New value: +"scheduled, finished or live, or a status as the API reports it, e.g. FT or NS; with team_id finished lists the latest first; with team_id and no status or date: latest results then next matches"
  5. Changed2 schema fields changed
    • changedInput schema / properties / status / description
      Previous value: -"match status filter as the API reports it, e.g. FT or NS"New value: +"scheduled, finished or live, or a status as the API reports it, e.g. FT or NS; with team_id finished lists the latest first"
    • addedInput schema / properties / team_id
      Added value: +{
      +  "description": "only this team's matches in every competition (team id from find_teams; not tennis); without a date all of them",
      +  "type": "integer"
      +}
  6. Changed1 schema field changed
    • changedInput schema / properties / game / description
      Previous value: -"esports: cs2, dota2 or lol"New value: +"esports: cs2, dota2, lol or valorant"
  7. Changed1 schema field changed
    • addedInput schema / properties / game
      Added value: +{
      +  "description": "esports: cs2, dota2 or lol",
      +  "type": "string"
      +}
  8. First observed

TDQS

A3.9/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 goes further by disclosing default scoping (today, UTC), result ordering rules for team queries, and that TV channel and highlights data may be included where known. It does not explain the non-idempotent hint (results change as matches go live/finish), which would have been the last useful piece.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is dense and front-loaded with essentially no filler, but the heavy nested-parenthesis structure makes the conditional logic hard to scan on first read. A short bulleted or semicolon-separated breakdown of the team_id/status combinations would have been clearer at the same length.

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?

For a 12-parameter tool with no output schema, the description covers the trickiest interactions and hints at return content. Paging behavior (offset/limit defaults) and the esports 'game' dimension are left entirely to the schema, which is acceptable given full schema coverage but is the remaining gap.

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 explaining interaction effects the schema lists only per-parameter: how team_id combines with status and dates, and that omitting all filters defaults to today. It adds real meaning about combined parameter behavior rather than restating individual fields.

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 opens with a concrete verb+resource: matches (fixtures and results) scoped by day, date range, league, or team, and it even previews return content (TV channels by country, highlights link). It is clearly a list/browse tool rather than a single-match lookup, but it never names or contrasts with obvious siblings such as get_live_matches or get_match_details, so differentiation is left to inference.

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?

Strong conditional guidance: no date/team means today (UTC); team_id alone yields latest results, then live, then next matches; team_id with status=scheduled yields only upcoming, with status=finished only recent results. What is missing is any explicit statement of when to prefer this tool over the live-match or single-match siblings.

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