Fantasy Football Draft Assistant

Best Available Price — this week's NFL props

best_available

Read-only

In season: where the best available PRICE is on this week's NFL props — strikes where Kalshi and the book consensus are 5¢+ apart. Free.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Max rows (default 15). Values above 50 are clamped to 50.
`roster`	No	Optional: player names on the USER's team — their strikes are shown first.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 7, 2026

addedInput schema / properties / limit

Added value: +{
+  "anyOf": [
+    {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "string"
+        }
+      ]
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Max rows (default 15). Values above 50 are clamped to 50."
+}

addedInput schema / properties / roster

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "string"
+    },
+    {
+      "additionalProperties": {},
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    }
+  ],
+  "description": "Optional: player names on the USER's team — their strikes are shown first."
+}

Changed7 schema fields changedSep 10, 2026

removedInput schema / properties / drafted

Removed value: -{
-  "description": "Player names already drafted (any team). Removed from the pool.",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedInput schema / properties / pick_number

Removed value: -{
-  "description": "The overall pick number that is 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 on the USER's team — enables a bye-stack warning on the top pick (byes are shown per-player regardless).",
-  "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: -[
-  "pick_number"
-]
```

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

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered by structured data. The description adds the "Free" cost signal and the Kalshi-vs-consensus sourcing, which is genuine extra context, but says nothing about ordering, freshness, or what happens when the market shifts.

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?

A single tight sentence with the scope front-loaded ("In season") followed by the key criterion and the pricing source. It is efficient, though the fragmentary style and trailing "Free." make it slightly clipped.

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?

For a read-only listing tool with annotations covering safety and a fully documented schema, the description is adequate but thin: there is no output schema, and the description never indicates what a returned row contains (strike, prices, gap size) or how results are ordered beyond the roster-first hint in the schema.

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% and there are only two optional parameters, so the schema fully documents limit (default 15, clamped at 50) and roster (user's players shown first). The description adds no parameter meaning beyond the schema, which is the baseline 3 case.

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?

The description names a concrete resource (this week's NFL props) and a precise selection criterion (strikes where Kalshi and the book consensus are 5¢+ apart), so an agent knows it is a mispricing-scan rather than a generic board. It does not explicitly name or distinguish itself from overlapping siblings like nfl_prop_edge or nfl_prop_board, which keeps it short of a 5.

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" gives an implicit precondition for use and the 5¢+ dev criterion explains what qualifies as a hit, but there is no when-not guidance and no named alternative among the many NFL/prop siblings. The agent must infer that the other prop tools serve different purposes.

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.

Best Available Price — this week's NFL props

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources