Skip to main content
Glama

Fantasy Football Draft Assistant

Kalshi vs Book-Consensus Gaps — this week's NFL props

adp_market_gaps
Read-only

In season: Kalshi vs book-consensus gaps on this week's NFL props, widest first, filter by position. Free. (ADP gaps return 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. Changed3 schema fields changed
    • removedInput schema / properties / limit
      Removed value: -{
      -  "default": 25,
      -  "description": "Max players to return, widest gap first (default 25). All 154 gaps are free.",
      -  "maximum": 400,
      -  "minimum": 1,
      -  "type": "integer"
      -}
    • 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."
      -}
  3. Changed8 schema fields changed
    • 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, widest gap first (default 25)."New value: +"Max players to return, widest gap first (default 25). All 154 gaps are 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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds 'Free' and the in-season availability window plus the widest-first default ordering, which is real behavioral context, but it says nothing about freshness of the consensus data, rate limits, or what happens when no props are on the board.

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 compact sentences with the seasonality gate and the core purpose front-loaded; the parenthetical about ADP is short and relevant. Near-optimal, with only mild asymmetry in how the season note interrupts the main clause.

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 two-optional-parameter read tool with no output schema, the definition covers purpose, ordering, filter scope and availability. It stops short of describing the returned row shape (player, prop, gap size), which an agent would otherwise have to discover at call time.

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%: the schema documents the limit default (15) and the 50-row clamp, and enumerates QB/RB/WR/TE/FLEX including the FLEX = RB/WR/TE expansion. The description only restates 'filter by position', adding essentially nothing beyond the schema, so the baseline of 3 applies.

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?

States a specific verb+resource: Kalshi-vs-book-consensus gaps on this week's NFL props, with default ordering (widest first) and an optional position filter. It is unambiguous what the tool returns and how it ranks results. It doesn't explicitly name the nearest siblings (nfl_prop_edge, nfl_prop_board), so an agent must infer the boundary itself.

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?

The 'In season' prefix and the parenthetical '(ADP gaps return in the 2027 offseason.)' implicitly tell the agent when this tool is applicable versus the out-of-season ADP variant. However no named alternative is offered for the in-season NFL-prop comparison case, and nothing says when not to use it.

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.