Fantasy Football MCP — Draft, Start/Sit, Waivers

Player This Week — Kalshi prop lines

player_outlook

Read-only

One NFL player this week — every Kalshi prop line, the best price across venues, and our probability at each strike. Free. Use for "is a good play this week", " props".

Input Schema

Name	Required	Description
`player`	No	Player name, full or partial (e.g. "Puka Nacua", "Bijan").
`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"
```

Changed3 schema fields changedSep 29, 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 / player

Added value: +{
+  "description": "Player name, full or partial (e.g. \"Puka Nacua\", \"Bijan\").",
+  "type": "string"
+}

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

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

Removed value: -{
-  "description": "Player full name (e.g. \"Bijan Robinson\", \"Jaxon Smith-Njigba\").",
-  "type": "string"
-}

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: -[
-  "player"
-]
```

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

A3.7/5.0

Behavior4/5

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

Annotations already establish readOnly/no-destruction and closed-world scope; the description adds genuine value by disclosing the return payload shape — all prop lines, the best price across venues, and modeled probability at each strike — plus that it is free. It doesn't cover behavior for ambiguous/partial player names, which is the one remaining 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?

Two tightly packed sentences with the scope and output contents front-loaded before the usage examples. The fragment 'Free.' earns its place as a pricing signal, though the quoted example phrasings at the tail are slightly loose.

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 three-optional-parameter, no-output-schema tool, the description usefully summarizes what comes back (lines, best price, strike-level probabilities), so the agent knows what to expect. Only the ambiguous-name behavior and relationship to adjacent explain_/edge tools are missing.

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 player formatting, the scoring enum with its half_ppr default, and platform-driven presets are already fully documented. The description adds nothing about any of the three parameters, so baseline 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 the resource precisely: one NFL player's Kalshi prop lines, best cross-venue price, and model probability at each strike. The 'One NFL player' scope implicitly separates it from board-level siblings like nfl_prop_board, though it never names those siblings explicitly.

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?

Provides example user utterances ('is <player> a good play this week', '<player> props'), which gives usable intent context. However, it offers no when-not guidance and doesn't route to the dense set of near-neighbors (nfl_prop_edge, nfl_prop_board, explain_prop, best_price), leaving the agent to infer boundaries.

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.

Player This Week — Kalshi prop lines

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources