Skip to main content
Glama

Fantasy Football MCP — Draft, Start/Sit, Waivers

by com.predictionmarketspicks
OverviewDiscussionsAdmin

Overpriced & Underpriced This Week

sleepers_and_busts
Read-only

Every NFL player whose Kalshi prop price our model disagrees with this week, ranked, marked underpriced or overpriced with the stat driving it. Free, the complete list. The strike, price and size are in Pro nfl_prop_edge. Use for "undervalued players this week", "who is the market overpricing", "sleepers this week", "busts to avoid this week".

Input Schema

NameRequiredDescriptionDefault
positionNoOptional position filter. One of: QB · RB · WR · TE.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changed
    • addedInput schema / properties / position
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "enum": [
+        "QB",
+        "RB",
+        "WR",
+        "TE"
+      ],
+      "type": "string"
+    }
+  ],
+  "description": "Optional position filter. One of: QB · RB · WR · TE."
+}
  3. Changed5 schema fields changed
    • 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"
-      ],
-      "type": "string"
-    }
-  ],
-  "description": "Optional position filter. One of: QB · RB · WR · TE."
-}
    • removedInput schema / properties / round
      Removed value: -{
-  "description": "Optional draft round filter (by league size, default 12-team).",
-  "maximum": 30,
-  "minimum": 1,
-  "type": "integer"
-}
    • 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"
-}
  4. 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"
+    ],
+    "type": "string"
+  }
+]
    • changedInput schema / properties / position / description
      Previous value: -"Optional position filter."New value: +"Optional position filter. One of: QB · RB · WR · TE."
    • removedInput schema / properties / position / enum
      Removed value: -[
-  "QB",
-  "RB",
-  "WR",
-  "TE"
-]
    • 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"
  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

A4.3/5.0
Behavior4/5

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

Annotations already cover the read-only/free safety profile, but the description adds real context beyond them: this is the free complete list while the price/size fields live in the Pro sibling, which materially affects whether an agent needs a second call. It does not describe return format or list size, keeping it short of a 5.

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 dense, front-loaded sentences: the result set and its annotation come first, the tier/alternative note second. The quoted example queries are useful but occasionally verbose; nothing is truly wasted.

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?

No output schema exists, so the description must carry the return shape, and it does reasonably: ranked list, under/over labels, the stat driving each call, and the caveat that price and size require the Pro tool. Fine for a zero-required-parameter read.

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 the single optional position filter is fully documented in the schema, including the allowed values. The description adds nothing about filtering behavior, so the baseline 3 applies.

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 resource (every NFL player whose Kalshi prop price the model disagrees with this week) plus the output shape: ranked, flagged underpriced/overpriced, with the driving stat. It also separates itself from the sibling nfl_prop_edge by noting that one carries strike/price/size while this is the free complete list.

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

Usage Guidelines5/5

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

Explicitly routes usage: it names the alternative Pro tool (nfl_prop_edge) for strike, price and size, and enumerates concrete activation phrasings like "undervalued players this week" and "busts to avoid this week." An agent can pick this tool without guessing.

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