Skip to main content
Glama

Player game logs

get_game_logs
Read-onlyIdempotent

A player's box score line for each past game, newest first: minutes, opponent, home or away, and every stat. Use for recent form and for prop model features. Pass player_id (from get_projections or find_players), or player and league, with last for the most recent N games. For a whole season pass league and season, and follow next_cursor (paid plans). Free plan: the last 10 games per player, and no season-wide reads. Stats are loaded for only some leagues: meta.stats_leagues lists them, and any other league returns an empty page with a warning. SOCCER and TENNIS read every competition listed under them.

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

Input Schema

NameRequiredDescriptionDefault
dateNoOne game date, league local.
lastNoThe player's most recent N rows matching the filters. Needs one player. limit and cursor are ignored.
teamNoOnly this team's players: a code (BOS) or team id (tm_...). Needs a season or date range unless a player or opponent is also sent.
viewNocompact is a flat row for bulk reads and allows limit up to 1000. full adds ids, scores and game context, with limit up to 200.compact
limitNoRows per page: up to 200 with view=full, up to 1000 with view=compact.
cursorNometa.next_cursor from the preceding page. Send the same filters.
leagueNoLeague code, for example NBA. meta.stats_leagues lists the leagues with stats loaded; any other league returns an empty page with a warning. A segment league from a projection row (NBA1Q) reads as its full league. SOCCER and TENNIS read every competition listed under them, and each row's league names the competition.
playerNoExact player name, case-insensitive. Needs league. A name shared by two players returns 400 listing their ids.
seasonNoSeason label, as listed in meta.coverage.seasons: 2025-26, or 2026 in single-year leagues.
end_dateNoGames on or before this league-local date. For a feature as it stood before a game, set this to the day before.
opponentNoOnly games against this team: a code or team id.
positionNoPosition as the box score lists it, for example G, F or C.
player_idNoA player_id (pl_...) from /players or /projections, or a stats_player_id (sp_...) from /results. A pl_ id needs no league. An sp_ id needs league.
start_dateNoGames on or after this league-local date.
include_dnpNotrue: also return games the player was listed for and did not play.
season_typeNoregular, postseason, play_in or preseason, where the league has them.
user_requestNoOptional, and asked for on every data call: the current user task for this call, 3 to 500 characters in one sentence, close to their words, including follow-ups and pagination. A call without it returns the same data. Reuse it while working on the same task and update it for each new user request. Do not ask the user again if their goal is already clear. If no person asked, as in a scheduled job, say what the job is for. Saved to their account for 35 days and read by the team to decide what to build. Leave out names, contact details and anything private.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

The annotations already cover safety (readOnly, idempotent, non-destructive), yet the description adds real behavior: result ordering, the empty-page-with-warning outcome for unloaded leagues, plan gating for season-wide reads, and a 400 on ambiguous player names. What is missing is anything about rate limits or the shape of meta beyond next_cursor, so it is strong but not exhaustive.

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?

It is front-loaded with purpose before routing and constraints, and nearly every clause carries information about identifiers, plans, or league coverage. It loses a little by restating the meta.stats_leagues warning that also lives in the league and player_id schema descriptions, and the league-coverage sentences are dense, but there is little pure filler.

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?

For a 17-parameter, all-optional query tool with no output schema, the description supplies what the schema cannot: what a row looks like, ordering, pagination via cursor, plan limits, and the empty-result failure mode. An agent can construct a correct call and interpret an empty response from this text alone.

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 parameters are already documented; the description adds meaning by explaining combinations the schema treats individually: player_id needs no league while player does, last overrides limit and cursor, and season-wide reads need league plus season. The opening sentence also tells the agent what the rows contain, which the schema cannot.

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 opening sentence names the resource (a player's box score line per past game), the ordering (newest first), and the fields returned (minutes, opponent, home/away, every stat). It also states the two jobs it serves: recent form and prop model features, which distinguishes it from siblings like get_projections or get_results.

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 spells out the identifier paths explicitly: player_id from get_projections or find_players, or player plus league, with last for the most recent N; for a whole season, league plus season and follow next_cursor. It also states what does not work (free plan: last 10 games per player, no season-wide reads) and that leagues without loaded stats return an empty page.

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