Skip to main content
Glama

Fantasy Football Draft Assistant

by com.predictionmarketspicks
OverviewDiscussionsAdmin

Overpriced & Underpriced This Week

sleepers_and_busts
Read-only

Every NFL player whose Kalshi prop price the PredictionMarketsPicks model disagrees with this week, ranked, each marked underpriced (model above the market) or overpriced (model below) with the stat driving it. Free, the complete list, no key. Which strike, at what price and by how much is the Pro nfl_prop_edge tool. Use for "undervalued players this week", "who is the market overpricing", "which players is the market wrong on", "overrated players week N", "where does your model disagree with the market most", "sleepers this week", "busts to avoid this week".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
positionNoOptional position filter. One of: QB · RB · WR · TE.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / position
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "enum": [
+        "QB",
+        "RB",
+        "WR",
+        "TE"
+      ],
+      "type": "string"
+    }
+  ],
+  "description": "Optional position filter. One of: QB · RB · WR · TE."
+}
  2. Changed5 schema fields changed
    • 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 / position
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "enum": [
-        "QB",
-        "RB",
-        "WR",
-        "TE"
-      ],
-      "type": "string"
-    }
-  ],
-  "description": "Optional position filter. One of: QB · RB · WR · TE."
-}
    • removedInput schema / properties / round
      Removed value: -{
-  "description": "Optional draft round filter (by league size, default 12-team).",
-  "maximum": 30,
-  "minimum": 1,
-  "type": "integer"
-}
    • 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"
-}
  3. Changed12 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 / position / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "enum": [
+      "QB",
+      "RB",
+      "WR",
+      "TE"
+    ],
+    "type": "string"
+  }
+]
    • changedInput schema / properties / position / description
      Previous value: -"Optional position filter."New value: +"Optional position filter. One of: QB · RB · WR · TE."
    • removedInput schema / properties / position / enum
      Removed value: -[
-  "QB",
-  "RB",
-  "WR",
-  "TE"
-]
    • removedInput schema / properties / position / 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"
  4. 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"
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already carry the safety profile (readOnly, non-destructive, closed-world), so the bar is lower. The description adds genuinely useful context beyond them: it is free, needs no key, and returns the complete (non-truncated) list, which affects how an agent should treat coverage.

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 purpose, the differentiator, and access facts before the query list. The seven quoted trigger phrases are somewhat repetitive, but each sentence still earns its place.

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 carries return-shape burden and does so reasonably: ranked list, underpriced/overpriced label, and the stat driving each call. Minor gaps (sort order, list size) remain but an agent can call it correctly.

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?

Only one optional parameter (position) and schema description coverage is 100%, so the schema fully documents it. The description adds nothing about the position filter, so the baseline 3 for high-coverage schemas applies.

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+resource: every NFL player whose Kalshi prop price the PredictionMarketsPicks model disagrees with this week, ranked, marked underpriced/overpriced with the driving stat. It distinguishes itself from the paid alternative by scoping to the complete disagreement list rather than strike-level detail.

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

Usage Guidelines5/5

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

Explicit when-to-use with concrete query phrasings ("undervalued players this week", "who is the market overpricing", "busts to avoid") and an explicit when-not/alternative: strike, price and magnitude live in the Pro nfl_prop_edge tool. Routing is unambiguous.

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