Skip to main content
Glama

List games

list_games
Read-onlyIdempotent

Use to list fixtures and results by season, stage, date, date range or club, newest first. For upcoming fixtures with lines use get_schedule; for one match in full use get_game. Costs 2 credits.

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": "list_games"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoTo date, YYYY-MM-DD.
dateNoOne date, YYYY-MM-DD (a UTC day unless timezone is given).
fromNoFrom date, YYYY-MM-DD.
teamNoClub id, abbreviation or name.
limitNoMax matches (default 50).
stageNoleague = league-table games (regular season, group stage, league phase); knockout = qualifying, knockout rounds and playoffs.
leagueNoLeague. Defaults to soccer. One of: soccer, mls, laliga, seriea, bundesliga, ligue1, ucl, championship, nwsl, ligamx, uel, uecl, eredivisie, primeira, scotland, brazil, argentina.
offsetNoPage offset; use next_offset.
seasonNoSeason by the year it starts: 2025 = 2025-26. MLS, the NWSL, Liga MX, Brazil and Argentina: the calendar year. Default: the latest.
statusNo
timezoneNoRead date, from and to as days in this IANA time zone (America/New_York, America/Mexico_City). Default UTC, where an evening kickoff in the Americas falls on the next day.

Output Schema

NameRequiredDescriptionDefault
noteNo
countYes
gamesYes
next_offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / date / description
      Previous value: -"One date, YYYY-MM-DD (UTC)."New value: +"One date, YYYY-MM-DD (a UTC day unless timezone is given)."
    • addedInput schema / properties / timezone
      Added value: +{
      +  "description": "Read date, from and to as days in this IANA time zone (America/New_York, America/Mexico_City). Default UTC, where an evening kickoff in the Americas falls on the next day.",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedOutput schema / properties / note
      Added value: +{
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description usefully adds what annotations cannot express: default ordering (newest first) and the credit cost of the call. It stops short of noting pagination behavior or the 200-item ceiling, which the schema covers but the description does not reinforce.

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?

Two sentences, zero filler, with the primary capability front-loaded and the disambiguation and cost trailing. Every clause carries actionable information.

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 11 optional parameters and an output schema present, the description does not need to explain return values, and it correctly focuses on selection and routing. The minor gap is that paging (limit/offset, next_offset) and the default result cap are not mentioned in prose, though the schema documents them.

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 91%, so nearly every parameter is already self-documenting, including the non-obvious timezone caveat and the season-year convention. The description only restates the filter dimensions at a high level and adds no syntax or edge-case guidance beyond the schema, so baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource ('list fixtures and results') plus the full set of filter dimensions (season, stage, date, date range, club) and the sort order ('newest first'). It also explicitly separates itself from get_schedule and get_game, so an agent can route without opening the schema.

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

Usage Guidelines5/5

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

Names two alternatives and the exact conditions that select them: get_schedule for upcoming fixtures with lines, get_game for a single match in full. Adding the 2-credit cost gives the agent a budget consideration alongside the routing rule.

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.