Skip to main content
Glama

Fantasy Football MCP — Draft, Start/Sit, Waivers

by com.predictionmarketspicks
OverviewDiscussionsAdmin

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

NameRequiredDescriptionDefault
limitNoMax rows (default 15).
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
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / limit / description
      Previous value: -"Max rows (default 15). Values above 50 are clamped to 50."New value: +"Max rows (default 15)."
  2. Changed2 schema fields changed
    • removedInput schema / properties / limit / anyOf
      Removed value: -[
-  {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "string"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / limit / type
      Added value: +[
+  "number",
+  "string",
+  "null"
+]
  3. 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."
+}
  4. 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."
-}
  5. 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"
  6. 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
  7. 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"
  8. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare this as a safe read-only, non-destructive, closed-world operation. The description adds useful behavior context such as 'Free', 'widest first' ordering, and seasonal availability, but it does not explain return fields, pagination, or data freshness beyond 'this week'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded with the in-season scope, then gives ordering, filtering, and a naming caveat. Every sentence carries useful information with no waste.

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 simple two-parameter read-only tool, it is mostly sufficient, but with no output schema it does not explain what a gap row contains, units, or return shape. The agent can call it, but the description leaves some result-interpretation gaps.

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 coverage is 100%, and both parameters are documented in the schema: limit has a default and position has an enum-like list. The description repeats 'filter by position' but adds no syntax or semantics beyond the schema, so baseline 3 is appropriate.

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 states a specific resource and scope: Kalshi vs book-consensus gaps on this week's NFL props, sorted widest first. It also clarifies the ADP-related naming caveat, so an agent can immediately tell what the tool returns.

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?

It gives an implied usage window ('In season') and notes that ADP gaps return in the 2027 offseason, but it does not explicitly say when to use this versus alternatives or what scenarios it is not for. Guidance is present but mostly implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Fantasy Football MCP — Draft, Start/Sit, Waivers toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources