Fantasy Football Draft Assistant

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. Free, no key. Use for " or this week", "compare and props", "who has the better prop, or ", " vs receiving yards".

Input Schema

TableJSON 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 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 and destructiveHint=false; the description adds 'Free, no key' (auth requirement) and details what the response contains (prop strikes, best price per side, model probability, ranked verdict). It does not mention rate limits or latency, so it falls 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?

Front-loads the core purpose and output contents before the example phrasings; every clause carries information. The trailing quoted examples add bulk but earn their place as routing cues.

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 return contents, and the input schema fully covers all three parameters. Missing only edge-case behavior (e.g., what happens with duplicate names or fewer than 2 players) to be fully complete.

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 with enums and defaults. The description only restates the 2–4 player bound, adding no new parameter semantics beyond the schema.

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 verb (compare), resource (2–4 NFL players this week), and enumerates the concrete outputs: Kalshi prop strikes, best price per side, published probability, and a ranked disagreement verdict. This is clearly distinguishable from the draft-oriented siblings like draft_board or who_do_i_draft.

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?

Gives explicit trigger phrasings ('<A> or <B> this week', 'compare <A> and <B> props', '<A> vs <B> receiving yards') that map user intent directly to this tool. No when-not guidance or named alternative is offered, but the intent coverage is strong.

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

All Fantasy Football Draft Assistant 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