Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nba_team_game_logs

Retrieve a team's per-game box-score log for a chosen season. Get field goals, rebounds, assists, steals, blocks, turnovers, points, and plus-minus for each game.

Instructions

Returns one team's game log for a season, one row per game with the team's box-score line (field goals, threes, rebounds, assists, steals, blocks, turnovers, points and plus-minus). Returns one team's game log for a season, one row per game with the team's box-score line (field goals, threes, rebounds, assists, steals, blocks, turnovers, points and plus-minus).

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

Input Schema

NameRequiredDescriptionDefault
seasonNoOptional season in YYYY-YY form; defaults to the current NBA season.
team_idYesRequired team id from nba-standings.
league_idNoOptional league id; only 00 (NBA) is verified.
season_typeNoOptional season type.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

C2.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden: it does disclose the return shape (one row per game with a named stat set), which is valuable given there is no output schema. It is silent on pagination, result limits, ordering, error behavior for an invalid or unverified league_id, and whether 'All Star' season_type changes the shape — gaps that matter for an unannotated read tool.

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

Conciseness2/5

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

The single sentence is repeated verbatim twice, which is pure waste with no added information or emphasis. The remaining content is front-loaded and clear, but the duplication is a real structural defect.

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

Completeness3/5

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

For a read-only per-season game-log tool with full schema coverage this is adequate: scope, row granularity, and returned stat categories are all stated, which matters because no output schema exists. It falls short on operational behavior (ordering, limits, league_id 'only 00 verified' caveat handling) that an unannotated tool should surface.

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 every parameter (season default, team_id provenance, league_id enum constraint, season_type enum) is already documented in the schema, giving a baseline of 3. The description contributes nothing further about parameter behavior, so it neither helps nor hurts.

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?

States a specific verb and resource ('Returns one team's game log for a season') and enumerates the row contents (one row per game, box-score line). It does not distinguish itself from plausible siblings such as nba_league_game_log or nba_player_game_logs, leaving a team-vs-league-vs-player ambiguity for the agent to resolve from names alone.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given, and no prerequisite beyond the schema's 'Required team id from nba-standings'. The agent gets no help choosing between this and team stat/dashboard siblings that also take a team_id and season.

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

Deploy Server

Other Tools