Skip to main content
Glama

LUMA NBA Impact Metrics

game_log

Read-onlyIdempotent

Box-score game log for a player and season (regular season or playoffs). last_n limits to the most recent games.

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": {
      "player": "<player>"
    },
    "name": "game_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
last_nNo
playerYes
seasonNo
season_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world profile, so the safety story is covered without the description. The text adds the season_type dual mode and the last_n truncation behavior, which is somewhat useful context, but it says nothing about return shape, ordering, or what happens when last_n is omitted.

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?

Two short sentences, with the core purpose front-loaded and the last_n qualifier immediately after. There is no redundant or filler wording, though the second sentence is clipped enough that it could carry the parameter semantics more explicitly at the same length.

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 four-parameter, no-output-schema read tool, the description is enough to identify the call but not enough to call it confidently. The undefined formats for player and season, and the unspecified behavior when last_n is absent, leave real gaps against the stated complexity.

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?

With 0% schema description coverage, the description has to carry the burden. It only covers season_type (regular vs playoffs) and last_n; it leaves 'player' and 'season' undocumented, so it is unclear whether player is an ID or a name, or what form the season integer takes (e.g. '2024' vs '2024-25').

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 a specific resource and scope: a box-score game log for a player and season. That is more precise than a restatement of the name, but it never distinguishes this from siblings such as game_ratings or player, so an agent still has to infer the boundary.

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

Usage Guidelines3/5

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

Usage is only implied: the parenthetical establishes that season_type selects regular season or playoffs, and the last_n sentence establishes a recency-limiting mode. There is no explicit when-to-use guidance and no mention of when to prefer a sibling tool instead.

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