Skip to main content
Glama

Five-Man Units & Team Without a Player (Pro)

lineups
Read-onlyIdempotent

Use this when the user asks which five-man units an NBA team plays most and how they rate, its best or worst lineups (also in the clutch), or how a team and each teammate did in the games a player missed. Returns, for a team_id, its five-man units by minutes together with their offensive, defensive and net ratings; with without_player_id, the games with and without him and each teammate's per-game minutes, points and usage on both sides, by the minutes gained. Requires Keel Stats Pro; the answer says so when the account has none. Not for one player's on/off: use player_splits_and_on_off.

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

Input Schema

NameRequiredDescriptionDefault
typeNoUnits of the regular season (default) or the playoffs.
phaseNoUnits over every minute ("all", default), the clutch, or without garbage time.
leagueNoLeague: "nba".nba
seasonNoOptional season year. Defaults to the current season.
team_idYesNumeric team ID from search.
min_minutesNoOptional: units with at least this many minutes together (default 20, the clutch 5).
without_player_idNoOptional numeric player ID: the team in the games he missed, against the games he played.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description isn't needed there. It still adds real context the annotations cannot convey: the Keel Stats Pro requirement and that the response self-reports missing entitlement, plus a summary of what each mode returns. Not a 5 because nothing is said about result size, limits, or failure modes beyond the paywall case.

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?

Front-loaded with the trigger conditions, then return semantics, then the entitlement caveat and the sibling exclusion — a sensible order with no filler sentences. It is a single dense run-on, which costs a little readability against a 5.

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?

With seven parameters but no output schema, the description carries the burden of describing returns, and it does so for both modes (unit-level ratings, and with/without plus per-teammate lines). Entitlement behavior and the sibling boundary are also covered, leaving nothing an agent needs before calling it.

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% and defaults/enums are already documented, so the baseline is 3. The description goes beyond it by explaining what without_player_id actually produces (with/without game splits and each teammate's minutes, points and usage ordered by minutes gained), which the schema's one-line entry does not make clear.

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 definition names specific verbs and resources: which five-man units a team plays most and how they rate, best/worst lineups including clutch, and team performance in games a player missed. It also explicitly excludes the adjacent concept ('Not for one player's on/off'), so an agent can separate it from player_splits_and_on_off without inspecting schemas.

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?

The opening clause is a direct trigger list ('Use this when the user asks...'), and the closing sentence gives an explicit when-not plus the named alternative. Both the positive and negative routing conditions are stated rather than implied.

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