Skip to main content
Glama

Pick'em lines: DraftKings Pick6 and PrizePicks vs BankrollSZN projections

invoke_pickem_board
Read-onlyIdempotent

Added after you connected: the first call asks you to approve it. DraftKings Pick6 and PrizePicks pick'em lines (More or Less) for NBA, NFL, NHL and UFC (PGA, WNBA, MLB and LoL in season), compared with BankrollSZN projections. Each row: player, team, opponent, stat, the pick'em line, the line type (PrizePicks standard, demon or goblin; Pick6 standard, alt ladder line or promo), the Pick6 multiplier, our projection, edge (projection minus line), our chance of More and Less (from our projection and a dispersion fitted on game logs), the best side, and the matching sportsbook line and price. Demon and goblin lines only take More. Pick'em contests are not sportsbook bets. Lines update every 20 minutes. Use it for questions like "best PrizePicks plays tonight", "is Jokic over 11.5 rebounds on Pick6 good", "Pick6 vs PrizePicks line for Tatum points".

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

Input Schema

NameRequiredDescriptionDefault
sideNoOnly rows where our best side is this. Default any.
siteNoDefault all (both sites).
statNoStat name or part of it, e.g. points, rebounds, shots, receiving yards, PRA.
limitNoMaximum rows. The plan limit applies on top.
sportNoDefault nba.
playerNoPlayer name or part of a name.
playersNoUp to 15 player names in one call. (maxItems: 15)
min_edgeNoOnly rows where |projection minus line| is at least this.
min_probNoOnly rows where our chance of the best side is at least this, 0 to 1.
line_typeNoDefault any.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations it discloses several non-obvious traits: an approval prompt on first call, lines refreshing every 20 minutes, the plan limit capping rows, and the one-sided nature of demon/goblin lines. It doesn't describe ordering of returned rows or failure modes, but the added context is substantial for a read-only tool.

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?

The approval-prompt note and data-freshness statement are front-loaded where they matter, and the long row-field enumeration is dense but each item informs interpretation. The single block could be split for scanability, but there is little true filler.

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 output schema, a 10-parameter schema, and no required parameters, the description compensates by fully describing the returned row shape and derived fields (edge, More/Less probabilities, best side). An agent has everything needed to choose it and interpret results.

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%, so the schema already carries the parameter burden and baseline is 3. The description does add domain meaning the enum values lack (demon/goblin lines only take More, Pick6 alt ladder vs promo) and defines edge as projection minus line, which slightly lifts it, but it doesn't explain min_prob or the limit/plan interaction beyond a passing mention.

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?

The description names the exact resources (DraftKings Pick6 and PrizePicks pick'em lines), the comparison baseline (BankrollSZN projections), and the sports covered, then enumerates the row fields. An agent can immediately tell this apart from the sim-picks and projections siblings.

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 concrete trigger questions ("best PrizePicks plays tonight", "is Jokic over 11.5 rebounds on Pick6 good") and clarifies that pick'em contests are not sportsbook bets, which scopes it away from sportsbook-line tools. It never explicitly names an alternative tool or a when-not-to-use case, so it stops short of full routing guidance.

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