Skip to main content
Glama

LUMA NBA Impact Metrics

lineups

Read-onlyIdempotent

Lineup groups (2-5 players together) for a team-season, or the groups a player is in. size 2-5 (default 5). No possession minimum (default sort = possessions; use min_poss to filter). sort: poss | net | ortg | drtg.

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

Input Schema

NameRequiredDescriptionDefault
sizeNo
sortNo
teamNo
limitNo
playerNo
seasonNo
min_possNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior in 'No possession minimum', warning that results are unfiltered by default and may include small-sample lineups, plus the default sort of possessions. It says nothing about result volume, ordering ties, or what an empty team/player call returns.

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?

Extremely dense and front-loaded: the resource definition comes first, then defaults, then the enum. Nothing is padded, though the telegraphic fragments ('size 2-5 (default 5)', 'sort: poss | net | ortg | drtg') read like shorthand notes rather than explanatory prose.

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

Completeness2/5

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

This is a 7-parameter tool with no schema descriptions, no required parameters and no output schema, so the description bears full responsibility. It omits how team vs player scoping works, what season and limit do, and whether any parameter is effectively mandatory, leaving the agent to guess at invocation shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% across 7 parameters, so the description must carry the load. It explains size (range 2-5, default 5), sort (values plus the default of poss) and min_poss, but leaves team, player, season and limit entirely undefined, and even the sort enumeration is just a restatement of schema values.

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 concrete resource and its grain: 'Lineup groups (2-5 players together) for a team-season, or the groups a player is in.' That distinguishes it from a plain player or game-log tool. It does not, however, differentiate itself from close siblings like wowy or onoff, which likely also return multi-player groupings.

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?

It gives operational guidance for filters ('use min_poss to filter', default sort = possessions) and implies the two entry points (team-season vs player). It never states when an agent should pick this over wowy, onoff or compare, nor what the preconditions are (e.g., that team or player should be supplied).

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