Fantasy Football MCP — Draft, Start/Sit, Waivers

Compare Players This Week — Kalshi prop lines

compare_players

Read-only

Compare 2–4 NFL players this week: every Kalshi prop strike each has, the best price per side across venues, our probability where we publish one, and a ranked verdict on whose price the model disagrees with most, and on which strike. Use for " or this week", "compare and props", "who has the better prop, or ", " vs receiving yards".

Input Schema

Name	Required	Description
`players`	No	2–4 player full names to compare.
`scoring`	No	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.
`platform`	No	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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026
- removedInput schema / $schema
```
Removed value: -"https://json-schema.org/draft/2020-12/schema"
```
Changed1 schema field changedOct 5, 2026
- removedInput schema / required
```
Removed value: -[
-  "players"
-]
```

Changed4 schema fields changedOct 2, 2026

addedInput schema / properties / platform

Added 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."
+}

addedInput schema / properties / players

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "string"
+    },
+    {
+      "additionalProperties": {},
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    }
+  ],
+  "description": "2–4 player full names to compare."
+}

addedInput schema / properties / scoring

Added 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."
+}

addedInput schema / required
```
Added value: +[
+  "players"
+]
```

Changed4 schema fields changedSep 10, 2026

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 / players

Removed value: -{
-  "anyOf": [
-    {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    {
-      "type": "string"
-    },
-    {
-      "additionalProperties": {},
-      "propertyNames": {
-        "type": "string"
-      },
-      "type": "object"
-    }
-  ],
-  "description": "2–4 player full names to compare."
-}

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 / required
```
Removed value: -[
-  "players"
-]
```

Changed13 schema fields changedSep 4, 2026

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 / players / anyOf

Added value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "additionalProperties": {},
+    "propertyNames": {
+      "type": "string"
+    },
+    "type": "object"
+  }
+]

removedInput schema / properties / players / items
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / players / maxItems
```
Removed value: -4
```
removedInput schema / properties / players / minItems
```
Removed value: -2
```
removedInput schema / properties / players / type
```
Removed value: -"array"
```

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"
```

Changed1 schema field changedAug 18, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedAug 11, 2026

TDQS

A4.1/5.0

Behavior4/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 real behavioral value by disclosing what comes back: per-strike best prices across venues, model probabilities only where published, and a ranked verdict — the caveat "where we publish one" correctly signals the probability field can be absent.

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?

Front-loaded with the core capability and output shape, then routed by short quoted user phrasings. The utterance list is somewhat long but each entry maps to a distinct query form, so it largely earns its space.

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?

With no output schema, the description compensates by enumerating the response contents (strikes, best price per side, probability, ranked verdict). an agent can anticipate the shape of the result; only cross-venue sourcing/pagination details are unstated, which matters little for a read-only comparison.

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%, so the schema already documents players, scoring, and platform in detail including enum lists. The description only restates the 2–4 player count and adds no extra syntax or format guidance, which is the expected baseline when the schema carries the load.

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?

A specific verb (compare) applied to a bounded resource (2–4 NFL players this week) with the output enumerated: prop strikes, best price per side, published probability, and a ranked disagreement verdict. That is clearly separable from siblings like explain_player or start_sit, which answer different questions.

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

Usage Guidelines4/5

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

The quoted example phrasings ("<A> or <B> this week", "who has the better prop", "<A> vs <B> receiving yards") give strong routing signals for when to pick this tool. It stops short of naming a sibling or a when-not-to-use condition, so not quite a 5.

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 tools Inspect

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.

Compare Players This Week — Kalshi prop lines

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources