Skip to main content
Glama

NBA player matchup tool

invoke_nba_matchup
Read-onlyIdempotent

Added after you connected: the first call asks you to approve it. The BankrollSZN NBA matchup tool for tonight: every player in the DraftKings pool with tonight's opponent, game total, spread, team implied points, salary, BankrollSZN projection, minutes, ownership, injury status and DK id, next to his season per game stats (minutes, points, rebounds, assists, steals, blocks, turnovers, shot volume and percentages) and season DK points per game. Give player for one player with his team and the opponent team profile (points, rebounds, assists, turnovers, shooting). view teams lists the team profiles. Use it to compare a player's season level with tonight's game environment.

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

Input Schema

NameRequiredDescriptionDefault
teamNoTeam abbreviation.
viewNoDefault players.
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.
positionNoFilter by DK position.
sort_dirNoDefault desc.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description does not contradict them. Beyond that it discloses a genuine runtime trait the annotations cannot express: 'the first call asks you to approve it', which prepares the agent for an unexpected consent step. It also previews the returned field set, which matters because no output schema exists, though it says nothing about pagination behavior beyond the schema's limit/offset hints.

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?

The opening billing/approval sentence is front-loaded but unrelated to selection, and the long comma-chained enumeration of a dozen stat fields reads as a data dump rather than a crisp description. The field list does carry information given there is no output schema, but it could be compressed into groups and the view-mode rules moved earlier so the agent hits the branching logic before the stat inventory.

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 8 optional parameters, no output schema, and four enumerated filters, the description does what it must: it describes the response shape in detail and clarifies the two view modes. What it leaves open is how the returned rows are structured (one row per player vs. a single-object response for the player query) and any indication of how large the default page is relative to the plan limit.

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%, so the baseline is 3. The description earns an extra point by explaining the interaction the schema cannot: supplying 'player' reshapes the response to a single player plus his team and the opponent team profile, and 'view: teams' switches to team-level profiles rather than a filtered player list. That is real semantic addition, though team/position/sort parameters get no elaboration beyond the schema text.

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 (tonight's DraftKings NBA player pool) and enumerates the paired datasets it joins: tonight's game environment (opponent, total, spread, implied points, salary, projection, ownership, injury status) against season per-game stats and season DK FPPG. That is far more than a restatement of the name. It does not, however, distinguish itself from the near-identically named sibling invoke_nba_player_matchup, so an agent has no stated basis for picking between them.

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

Usage Guidelines4/5

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

It gives a clear purpose statement — 'Use it to compare a player's season level with tonight's game environment' — and routes between the two modes by explaining that passing a player yields that player plus opponent team profile while 'view teams lists the team profiles'. What is missing is any exclusion or named alternative: with siblings like invoke_nba_player_matchup, invoke_nba_player_pool, and invoke_nba_player_index available, the agent gets no guidance on when this tool is the wrong choice.

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