Skip to main content
Glama

List games

aura_list_games
Read-onlyIdempotent

Games for one day with teams, start time, status and score. Omit date for today (US Pacific league date). Filter by sport, status or team abbreviation. Returns Aura game ids for the other game tools; for odds, pass each id to aura_game_markets.

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

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD league date; defaults to today
teamNoTeam abbreviation, e.g. NYY
sportNo
cursorNopage.nextCursor from the previous call
statusNo
pageSizeNoDefaults to 25

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / status / enum
      Previous value: -[
      -  "scheduled",
      -  "in_progress",
      -  "final"
      -]New value: +[
      +  "scheduled",
      +  "in_progress",
      +  "pending_final",
      +  "final"
      +]
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world behavior, so the safety profile is covered. The description adds the useful nuance that the default date is the US Pacific league date and that results carry Aura game ids usable by other tools. It does not explain pagination behavior or result ordering beyond what the cursor/pageSize schema shows.

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?

Three short sentences, front-loaded with what the tool returns, followed by filtering and the cross-tool routing hint. The opening is a sentence fragment, but there is no filler.

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 six-parameter, all-optional, read-only list tool with no output schema, the description covers the return shape, the date default, filtering, and follow-on routing. Only pagination semantics and precise ordering remain unstated.

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 67%, so most parameters are already documented, including date, team, cursor and pageSize. The description restates the date default and filterable fields but adds no enum meanings for sport or status beyond the schema's own values.

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 names the resource (games), the scope (one day), and the fields returned (teams, start time, status, score), and it distinguishes itself from aura_game_markets by saying ids feed odds lookups. It does not distinguish itself from near-siblings like aura_live_games or aura_get_game, so it falls short of a 5.

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?

It gives concrete operating guidance: omit date for today, filter by sport/status/team, and pass returned ids to aura_game_markets for odds. It lacks explicit when-not-to-use guidance against aura_live_games (live-only) or aura_get_game (single game by id).

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.