Skip to main content
Glama
Sign In

Keel Stats

by com.keelstats.api
OverviewDiscussionsAdmin

Find a Team’s Game

find_game
Read-onlyIdempotent

Use this when the user asks about one team's game on a date, its next or last game, or a specific meeting ('Lakers next game', 'Cowboys vs Eagles on November 23') and you need its game_id. Returns the team's game on that date, or its last three finished and next three games, with game_id, start time, state, week (NFL), each side's team (id and abbreviation) and score, and the pair's matchup page; each game's page is game_url with its id in place of {id}. Not for the whole slate (tonight_slate) or the history of a pair (head_to_head).

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": {
      "league": "<league>",
      "team_id": "<team_id>"
    },
    "name": "find_game"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoOptional US Eastern game day, YYYY-MM-DD (e.g. "2026-11-23"). Omit for the last three and next three games.
leagueYesLeague ("nba" or "nfl").
team_idYesNumeric team ID from search.
opponent_idNoOptional numeric team ID of the opponent, from search: only the games between the two.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish that this is a safe, idempotent read-only lookup, but the description adds useful behavioral detail about what is returned: the game on the date or the last three finished and next three games, with team IDs, abbreviations, scores, state, and week. It also explains the game_url template and scopes the result to one team or a specific meeting, though it does not mention pagination or rate limits.

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?

The description is front-loaded with the use case, then return behavior, then exclusions. It is dense and includes examples and URL-template detail, but nearly every sentence earns its place; the return-value sentence is long but informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Even though there is no output schema, the description explains the returned fields and URL structure well enough for an agent to use the result. Combined with the fully documented input schema and sibling exclusions, it gives a complete picture of when and how to call the tool.

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 the input schema already documents date, league, team_id, and opponent_id semantics. The description reinforces the date behavior and the specific-meeting use case, but it does not add syntax or constraints beyond what the schema provides.

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?

The description states a specific verb and resource: find one team's game and retrieve its game_id. It clearly distinguishes this from whole-slate and pair-history tools by naming tonight_slate and head_to_head as exclusions.

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?

It gives explicit when-to-use conditions: one team's game on a date, next or last game, or a specific meeting such as 'Lakers next game' or 'Cowboys vs Eagles on November 23'. It also states when not to use it, naming the sibling alternatives for the whole slate and pair history.

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

All Keel Stats toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources