Skip to main content
Glama

Fantasy Football MCP — Draft, Start/Sit, Waivers

by com.predictionmarketspicks
OverviewDiscussionsAdmin

Your Roster's Props This Week

who_do_i_draft
Read-only

In season: the Kalshi props listed on the players you name (2–4), with the best price per strike. Free. Pass roster: ['Player A', 'Player B'].

Input Schema

NameRequiredDescriptionDefault
rosterNo2–4 player names on your roster (full or partial).

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 / roster
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "string"
+    },
+    {
+      "additionalProperties": {},
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    }
+  ],
+  "description": "2–4 player names on your roster (full or partial)."
+}
  3. Changed7 schema fields changed
    • removedInput schema / properties / drafted
      Removed value: -{
-  "description": "Player names already drafted by ANY team. Optional — without it the board is estimated from pick_number using consensus ADP. Supplying it is always more accurate.",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
    • removedInput schema / properties / pick_number
      Removed value: -{
-  "description": "The overall pick number on the clock.",
-  "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 / roster
      Removed value: -{
-  "description": "Player names already on the user's team.",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
    • 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"
-}
    • removedInput schema / required
      Removed value: -[
-  "roster",
-  "pick_number"
-]
  4. Changed8 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 / 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
    • addedInput schema / properties / drafted
      Added value: +{
+  "description": "Player names already drafted by ANY team. Optional — without it the board is estimated from pick_number using consensus ADP. Supplying it is always more accurate.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  6. 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"
  7. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds two pieces of genuinely non-structured context — the in-season gating and the fact that calls are free — plus that results are deduplicated to the best price per strike. It does not say what happens out of season or when a named player isn't found, which is the main remaining behavioral gap.

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?

Very short with no filler, and the example is placed at the end where it belongs. The front-loading is weaker — the first clause is a condition ("In season:") rather than the tool's function, and the "Free." sentence fragment reads as loose note-taking rather than structured spec.

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?

With one optional parameter, full schema coverage, annotations, and no output schema, the definition has modest burden — yet it is thin. An agent still doesn't know the result shape (how many props per player, ranked how), out-of-season behavior, or unmatched-name handling.

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 roster parameter already documents "2–4 player names (full or partial)". The "Pass roster: ['Player A', 'Player B']" example adds modest value by resolving the anyOf ambiguity toward the array form, but nothing else is added 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 Kalshi props listed on the players you name (2–4), with the best price per strike" does state the resource (props for named players) and an output property (best price per strike). However, the tool name and title ("who_do_i_draft", "Your Roster's Props This Week") suggest draft recommendations, and the description never resolves that tension or positions itself against siblings like player_outlook or draft_board.

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?

"In season" is an implied usage condition and "Free" signals a cost-free call, which is useful routing context. But no alternative is named and there is no statement of when NOT to use it (e.g., out of season, or for non-prop questions that belong to player_outlook or compare_players).

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