Skip to main content
Glama

NBA ownership by contest type

invoke_nba_ownership_by_contest
Read-onlyIdempotent

Added after you connected: the first call asks you to approve it. BankrollSZN NBA DraftKings projected ownership for one classic slate, adjusted by contest type: 150-Max (the published baseline from the field lineup simulation), 20-Max, 3-Max, Single Entry or Cash. Each row has the 150-Max ownership, the contest-type ownership, the change, salary, projection and DK id. Same numbers as the Contest Type menu on the NBA Projections page: Cash and 3-Max come from their own field simulations; 20-Max and Single Entry use ownership buckets of 5% with a multiplier measured from contest results, then the pool is scaled back to the 150-Max total. Every value is capped at 100. Defaults to the main slate.

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

Input Schema

NameRequiredDescriptionDefault
teamNoTeam 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 own (contest-type ownership).
positionNoFilter by DK slot.
slate_idNoDraftKings slate id from nba_list_slates. Default the main slate.
include_outNoKeep players ruled out. Default false.
contest_typeNoDefault 20max.

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 establish readOnly/idempotent/non-destructive, so the description is not the safety carrier, but it adds real behavior the schema cannot: the first call triggers an approval prompt, every value is capped at 100, only one classic slate is covered, and it defaults to the main slate. It also discloses how 20-Max and Single Entry numbers are derived (5% buckets plus a measured multiplier, then rescaled to the 150-Max total), which tells the agent how much to trust those columns. No return shape or pagination behavior is described beyond the schema, keeping it at a 4.

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?

One compact paragraph that opens with the resource and scope before the derivation detail, so an agent scanning the first clause gets the point. The methodology sentences about field simulations and ownership buckets are long but earn their place by explaining why contest-type numbers differ from baseline ownership. The approval-prompt note is slightly awkward as the opening clause but costs only a few words.

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 nine optional parameters, no output schema, and a read-only profile, the description covers everything needed to call and interpret it: what a slate scope means, the contest-type semantics, the default, the approval flow, and an explicit row-by-row field list (150-Max ownership, contest-type ownership, change, salary, projection, DK id) that substitutes for a missing output schema. Nothing material for correct invocation is absent.

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% with all nine parameters documented, so the baseline is 3. The description still adds meaning the schema does not: it explains what '150max' means versus the other contest types and how each is computed, which directly informs the most consequential enum choice. It reinforces the main-slate default but adds nothing new for team, player, limit, offset, sort_by, position, or include_out.

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 gives a specific verb and resource: projected DraftKings ownership for one classic slate, adjusted by contest type, with five named contest-type variants. It implicitly positions itself against the broader NBA Projections tool by saying the output matches the 'Contest Type menu on the NBA Projections page,' so an agent can tell it is the ownership-specific view rather than raw projections. It stops short of an explicit 'use this instead of' statement, which keeps it off a 5.

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 rather than stated: the tool is for pulling contest-type-adjusted ownership on a slate, and the description explains what each contest type means numerically so an agent can pick a 'contest_type' value intelligently. There is no explicit when-to-use/when-not-to-use framing and no pointer to a sibling for the case where the agent wants plain projections instead.

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