Skip to main content
Glama

Fantasy Football Draft Assistant

NFL Prop Market Board — this week (the draft board returns in 2027)

draft_board
Read-only

In season: this week's NFL prop market board — every Kalshi player prop with the best price across venues, filter by position. Free. (The 2026 fantasy draft board returns in the 2027 offseason.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax rows (default 15). Values above 50 are clamped to 50.
positionNoOptional position filter (FLEX = RB/WR/TE). One of: QB · RB · WR · TE · FLEX.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "anyOf": [
      +    {
      +      "anyOf": [
      +        {
      +          "type": "number"
      +        },
      +        {
      +          "type": "string"
      +        }
      +      ]
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Max rows (default 15). Values above 50 are clamped to 50."
      +}
    • addedInput schema / properties / position
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "enum": [
      +        "QB",
      +        "RB",
      +        "WR",
      +        "TE",
      +        "FLEX"
      +      ],
      +      "type": "string"
      +    }
      +  ],
      +  "description": "Optional position filter (FLEX = RB/WR/TE). One of: QB · RB · WR · TE · FLEX."
      +}
  2. Changed5 schema fields changed
    • removedInput schema / properties / limit
      Removed value: -{
      -  "default": 50,
      -  "description": "Max players to return, best first (default 50). The full board is ~330 and all of it is free.",
      -  "maximum": 400,
      -  "minimum": 1,
      -  "type": "integer"
      -}
    • removedInput schema / properties / platform
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "enum": [
      -        "yahoo",
      -        "espn",
      -        "sleeper",
      -        "nfl",
      -        "cbs",
      -        "fantrax",
      -        "draftkings",
      -        "underdog"
      -      ],
      -      "type": "string"
      -    }
      -  ],
      -  "description": "League platform — applies its default scoring, size, roster + best-ball settings (overridable by explicit scoring/teams). Underdog/DraftKings are best ball. One of: yahoo · espn · sleeper · nfl · cbs · fantrax · draftkings · underdog."
      -}
    • removedInput schema / properties / position
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "enum": [
      -        "QB",
      -        "RB",
      -        "WR",
      -        "TE",
      -        "FLEX"
      -      ],
      -      "type": "string"
      -    }
      -  ],
      -  "description": "Optional position filter (FLEX = RB/WR/TE). One of: QB · RB · WR · TE · FLEX."
      -}
    • removedInput schema / properties / scoring
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "enum": [
      -        "standard",
      -        "half_ppr",
      -        "ppr"
      -      ],
      -      "type": "string"
      -    }
      -  ],
      -  "description": "Scoring format: standard, half_ppr (default), or ppr (full PPR). Overrides a platform preset. Works for Yahoo/ESPN/Sleeper defaults. One of: standard · half_ppr · ppr."
      -}
    • removedInput schema / properties / teams
      Removed value: -{
      -  "description": "League size (number of teams) for draft-round math. Overrides the platform default; falls back to 12.",
      -  "maximum": 20,
      -  "minimum": 4,
      -  "type": "integer"
      -}
  3. Changed12 schema fields changed
    • addedInput schema / properties / platform / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "enum": [
      +      "yahoo",
      +      "espn",
      +      "sleeper",
      +      "nfl",
      +      "cbs",
      +      "fantrax",
      +      "draftkings",
      +      "underdog"
      +    ],
      +    "type": "string"
      +  }
      +]
    • changedInput schema / properties / platform / description
      Previous value: -"League platform — applies its default scoring, size, roster + best-ball settings (overridable by explicit scoring/teams). Underdog/DraftKings are best ball."New value: +"League platform — applies its default scoring, size, roster + best-ball settings (overridable by explicit scoring/teams). Underdog/DraftKings are best ball. One of: yahoo · espn · sleeper · nfl · cbs · fantrax · draftkings · underdog."
    • removedInput schema / properties / platform / enum
      Removed value: -[
      -  "yahoo",
      -  "espn",
      -  "sleeper",
      -  "nfl",
      -  "cbs",
      -  "fantrax",
      -  "draftkings",
      -  "underdog"
      -]
    • removedInput schema / properties / platform / type
      Removed value: -"string"
    • addedInput schema / properties / position / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "enum": [
      +      "QB",
      +      "RB",
      +      "WR",
      +      "TE",
      +      "FLEX"
      +    ],
      +    "type": "string"
      +  }
      +]
    • changedInput schema / properties / position / description
      Previous value: -"Optional position filter (FLEX = RB/WR/TE)."New value: +"Optional position filter (FLEX = RB/WR/TE). One of: QB · RB · WR · TE · FLEX."
    • removedInput schema / properties / position / enum
      Removed value: -[
      -  "QB",
      -  "RB",
      -  "WR",
      -  "TE",
      -  "FLEX"
      -]
    • removedInput schema / properties / position / type
      Removed value: -"string"
    • addedInput schema / properties / scoring / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "enum": [
      +      "standard",
      +      "half_ppr",
      +      "ppr"
      +    ],
      +    "type": "string"
      +  }
      +]
    • changedInput schema / properties / scoring / description
      Previous value: -"Scoring format: standard, half_ppr (default), or ppr (full PPR). Overrides a platform preset. Works for Yahoo/ESPN/Sleeper defaults."New value: +"Scoring format: standard, half_ppr (default), or ppr (full PPR). Overrides a platform preset. Works for Yahoo/ESPN/Sleeper defaults. One of: standard · half_ppr · ppr."
    • removedInput schema / properties / scoring / enum
      Removed value: -[
      -  "standard",
      -  "half_ppr",
      -  "ppr"
      -]
    • removedInput schema / properties / scoring / type
      Removed value: -"string"
  4. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max players to return, best first (default 50)."New value: +"Max players to return, best first (default 50). The full board is ~330 and all of it is free."
    • changedInput schema / properties / limit / maximum
      Previous value: -100New value: +400
  5. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  6. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds that the board is 'Free' and that it is seasonally active, plus that the draft board is dormant until 2027 — useful context, but no disclosure of refresh cadence, data source lag, or empty-state behavior.

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?

Two tight sentences with the operational content front-loaded; the parenthetical about the 2027 draft board is arguably necessary to resolve the name/behavior mismatch. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-param read-only board with no output schema, the description conveys the return concept (all Kalshi player props priced across venues) and the seasonal gating. It still leaves the relationship to 'nfl_prop_board' and the practical limits of the result set unexplained.

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% with both parameters fully documented, so the baseline is 3. The description only echoes the position filter ('filter by position') and says nothing about the limit parameter or its 50-row clamp, adding no meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description does state a concrete verb+resource: 'this week's NFL prop market board — every Kalshi player prop with the best price across venues.' However, the tool name 'draft_board' and title ('the draft board returns in 2027') point at a different resource, so an agent reading the name first will be misled before reaching the sentence that clarifies the actual behavior.

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

Usage Guidelines2/5

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

'In season:' hints at a temporal condition, but no explicit when-to-use rule, no prerequisites, and no exclusion. Critically, the sibling 'nfl_prop_board' is not mentioned, even though it sounds like it could serve the same purpose, leaving the agent unable to choose between them.

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.