Skip to main content
Glama

NBA scheme and size matchups tonight

invoke_nba_scheme_matchups
Read-onlyIdempotent

Added after you connected: the first call asks you to approve it. Tonight's NBA scheme and size matchups from BankrollSZN: every projected player with his opponent's scheme (Drop heavy, Switch heavy, Mixed), drop and switch scores, opponent size (players 6-9+ on the floor) and size style, his own drop killer, switch killer and roll threat scores, BankrollSZN projected minutes and DK points, and matchup flags: Pull-up shooter vs drop team, Pull-up shooter vs switch team, Iso scorer vs switch team, Roll man vs drop team, Big vs small-ball team, Big vs big team, Small guard vs big team. Context only; the flags do not change BankrollSZN projections.

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_scheme_matchups"
  }
}

Input Schema

NameRequiredDescriptionDefault
flagNoany (default) = only flagged players. none_ok = all players. Or one flag type.
teamNoTeam or opponent abbreviation.
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.
sort_byNoDefault proj_fpts.
sort_dirNoDefault desc.
min_minutesNoMinimum projected minutes. Default 10.

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 cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely new context: the first call requires user approval, and the flags are informational rather than projection-altering. Pagination and plan-limit behavior are surfaced only in the schema, not the description, which keeps it off 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?

Content is front-loaded but delivered as one very long comma-chained sentence that mixes data fields, matchup flags, and a caveat. Because there is no output schema, the field enumeration earns its place, though a bulleted or grouped structure would make the return shape far easier to scan.

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 and eight all-optional parameters, the description does the heavy lifting by spelling out exactly what each row contains, including the seven flag types and the projection fields. Missing are pagination mechanics and any hint about row volume or rate/plan limits, which matter given offset and limit parameters.

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%, with enums and defaults documented inline for flag, sort_by, and sort_dir, so the schema carries the parameter burden. The description enumerates returned fields rather than adding meaning to any parameter; the crucial distinction that 'any' means flagged-only while 'none_ok' returns all players lives in the schema, not the prose.

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 the exact resource (tonight's NBA scheme and size matchups) and enumerates the payload: opponent scheme (Drop/Switch/Mixed), drop and switch scores, opponent size, and seven named matchup flags. That is far more specific than the name or title alone. It stops short of distinguishing itself from nearby siblings such as invoke_nba_player_matchup or invoke_nba_defensive_schemes, so an agent must infer which tool answers the adjacent question.

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: 'Context only; the flags do not change BankrollSZN projections' tells the agent this is a read-for-insight tool, not a projection modifier, and the approval note warns about a first-call prompt. There is no explicit statement of when to reach for this versus the other NBA matchup tools, and no exclusions.

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