Skip to main content
Glama

DFS results: projections and ownership vs actual

invoke_dfs_results
Read-onlyIdempotent

Added after you connected: the first call asks you to approve it. DraftKings DFS results for past slates, calculated by BankrollSZN. For each slate: our locked projection and projected ownership (pOWN, frozen at first lock) against actual DK fantasy points and actual field ownership by contest type (150-Max, 20-Max, 3-Max, Single Entry, Cash), taken from the full contest field. Also the contest outcomes: winning score, cash line, score percentiles, entries and the winning lineup (with each player's points and ownership). Sports: nba, nhl, nfl (DK classic main slates with a captured contest). view summary (default): contests, winning lineups, top scorers, biggest beats and busts vs projection, chalk results, best value per $1K and projection accuracy. view players: the full player table, sortable. view contests: contest outcomes only. Give player for one player (no date = his last 10 slates). Use it for questions like "what won last night", "what was the cash line", "who was the chalk and did it hit", "how did your projections do", "how did Jokic do vs projection". Not for upcoming slates.

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

Input Schema

NameRequiredDescriptionDefault
dateNoSlate date YYYY-MM-DD (NFL: the Sunday). Default = the latest graded slate. "yesterday" also works.
teamNoTeam abbreviation filter (players view).
viewNoDefault summary. dates lists the slate dates on file.
limitNoMaximum rows. The plan limit applies on top.
sportNoDefault nba.
playerNoPlayer name, or part of a name. Without date: that player across his last 10 slates.
sort_byNoplayers view sort. Default actual. beat = actual minus projection, bust = projection minus actual, value = actual points per $1K.
positionNoPosition filter, e.g. PG, C, QB, WR, D, G (players view).
slate_idNoOnly this DK draft group when a date has more than one slate.
contest_typeNoOwnership column to use for own and own_vs_pown. Default 150max.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description still adds real context: an approval prompt on first invocation, that pOWN is frozen at first lock (so numbers won't move), that field ownership comes from the full contest field, and that data exists only where a contest was captured. Weaknesses: the description lists sports as 'nba, nhl, nfl' while the schema enum also allows mlb, and nothing is said about the plan limit referenced in the schema.

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?

Purpose and the approval caveat are front-loaded, and every sentence carries payload rather than filler. It is a dense monolith of roughly 200 words with no paragraph or bullet breaks, so the view definitions and use-case examples are harder to scan than they need to be.

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?

For a 10-parameter, fully-optional tool with no output schema, the description does the heavy lifting: it explains what each view returns, per-slate record contents, sport coverage and default behavior. Gaps are the mlb enum mismatch, unexplained 'plan limit' interaction with limit, and no note on response size or how many slates a bare no-date call spans.

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 schema already defines every parameter and the baseline is 3; the description nonetheless adds view-specific semantics the enum cannot carry (summary = contests, winning lineups, top scorers, beats/busts, chalk results, value per $1K, projection accuracy; players = full sortable table). It also re-states interaction rules like 'no date = his last 10 slates' that materially change how player is used.

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 plus scope: DraftKings DFS *results* for *past* slates, with the exact payload enumerated (locked projection and frozen pOWN vs. actual DK points and actual field ownership by contest type, plus contest outcomes). The 'Not for upcoming slates' boundary makes it unmistakable against the projection/optimizer siblings without naming 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?

Provides five concrete example questions ('what was the cash line', 'who was the chalk and did it hit', 'how did Jokic do vs projection') and an explicit exclusion ('Not for upcoming slates'), which is strong when/when-not coverage. It never names the alternative tool an agent should use for upcoming slates, so the routing half is left implicit.

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