Skip to main content
Glama

NBA DraftKings slates

invoke_nba_list_slates
Read-onlyIdempotent

Added after you connected: the first call asks you to approve it. Lists the NBA DraftKings classic slates BankrollSZN has built for the current day: slate_id, number of games and players, and the default (main) slate. Pass slate_id from here to nba_projections, nba_player_pool, nba_optimizer and nba_ownership_by_contest.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/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 triggers an approval prompt after connecting. It also discloses the 'current day' scope limit, which tells the agent historical slates are not returned. It does not say what happens when no slates have been built yet (empty result vs error) or mention auth/rate limits.

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?

Three compact sentences with no filler, and the enumeration of return fields plus the downstream handoff are both load-bearing. The approval-prompt sentence is placed first, which is slightly awkward since the tool's identity is disclosed second; front-loading what the tool lists would read better.

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 no parameters and no output schema, the description carries the return-value burden and does so explicitly (slate_id, games, players, default/main slate), while annotations cover safety. For a parameterless list tool, an agent has everything needed to call it and to use the result.

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?

Zero input parameters, so the baseline is 4 and there is no schema semantics to add to. The description still adds useful meaning by identifying slate_id as the key this tool emits and the identifier the four downstream nba_* tools consume, which clarifies the data contract rather than a parameter.

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?

States a specific verb and resource ('Lists the NBA DraftKings classic slates BankrollSZN has built') plus the scope ('for the current day'), and enumerates what comes back (slate_id, game/player counts, default slate). This clearly separates it from invoke_fd_slates and the other sport-specific list_slates variants without the agent needing to open a schema.

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?

Gives explicit downstream routing: 'Pass slate_id from here to nba_projections, nba_player_pool, nba_optimizer and nba_ownership_by_contest.' That is strong workflow guidance and establishes this as the entry point for NBA DK workflows. It stops short of naming when not to use it (e.g., FanDuel slates via invoke_fd_slates, or other sports), leaving that to inference from the sport/operator wording.

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