Skip to main content
Glama

NBA defensive schemes and scheme traits

invoke_nba_defensive_schemes
Read-onlyIdempotent

Added after you connected: the first call asks you to approve it. BankrollSZN NBA defensive scheme board. view teams (default): all 30 teams with a scheme label (Drop heavy, Switch heavy or Mixed), drop score, switch score, size style (Plays big, Balanced, Plays small), night to night size change, players 6-9+ on the floor, average height, how often bigs guard guards, opponent mid-range, rim and three shares, and points per possession allowed to pick-and-roll ball handlers, roll men and isolations. view players: each player's scheme traits: drop killer (pull-up shooting volume and accuracy plus pick-and-roll ball handling), switch killer (isolation volume and efficiency), roll threat, with the pull-up and play-type stats behind them. Same data as bankrollszn.com/nba-defensive-schemes, refreshed daily.

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

Input Schema

NameRequiredDescriptionDefault
teamNoTeam abbreviation.
viewNoDefault teams.
limitNoMaximum rows to return. The plan limit applies on top.
offsetNoPaid plans: next page offset from page.next_offset.
playerNoPlayer name, or part of a name (players view).
schemeNoTeams view filter.
sort_byNoDefault drop_score (teams) or drop_killer (players).
sort_dirNoDefault desc.
size_groupNoPlayers view filter: small = 6-5 or shorter, big = 6-9 to 6-10, c7 = 6-11+.
size_styleNoTeams view filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish this as a safe, idempotent read, so the bar is lower; the description adds genuinely new behavior: data is refreshed daily, it mirrors a specific public URL, and the first call triggers an approval prompt after connection. It does not mention rate limits or result-size ceilings (limit/plan caps are only in the schema), which keeps it from a 5.

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

Conciseness3/5

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

It is a single dense run-on paragraph front-loaded with a meta note about the approval prompt rather than the tool's purpose, which weakens front-loading. For 10 parameters the length is defensible, but the long comma-chained field lists would be far easier to scan as bullets.

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

Completeness4/5

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

With no output schema, the description correctly compensates by enumerating the returned metrics for both views, including the definitions of drop killer, switch killer and roll threat, which an agent otherwise could not know. It is close to complete for a read-only analytics tool; only pagination and plan-cap behavior are left implicit in the schema.

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%, including enum explanations and defaults, so the schema already carries parameter meaning and the baseline is 3. The description reinforces defaults for the view ('teams') and clarifies what the two views return, but adds no syntax, format, or interaction details (e.g., how team, scheme and size_style combine, or that offset comes from page.next_offset) beyond the schema.

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 (NBA defensive scheme board) and enumerates two concrete output shapes: team rows with scheme labels, drop/switch scores and size style, and player rows with drop killer, switch killer and roll threat traits. That is far more specific than a restated title, but it never names or contrasts a sibling such as invoke_nba_scheme_matchups, so an agent must infer positioning from the field lists alone.

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 implied through 'view teams (default)' versus 'view players', which tells the agent which view to select for team-level versus player-level data. There is no explicit when-to-use versus when-not-to-use guidance relative to the many related NBA tools, and no stated prerequisites beyond the approval note.

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