Skip to main content
Glama

Prediction Markets Quant

by com.predictionmarketspicks
OverviewDiscussionsAdmin

NFL Player Prop Edge (model vs Kalshi)

nfl_prop_edge
Read-only

Use for "best NFL props today" and "receiving yards prop value". Our projection vs the Kalshi "X or more" prop line: the contract, the YES/NO call, our odds and Kalshi's price for that side, the projection and the edge, with WATCH rows labelled. Live in season. Pro — sign in with PredictionMarketsPicks, or a Pro API key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax rows (default 10). Values above 25 are clamped to 25.
minEdgeNoMin absolute edge in pp (default 5). Accepts a number or a numeric string ("3", "3pp", "3%").
propTypeNoOptional filter by prop type. One of: pass_yds · pass_tds · rush_yds · rec_yds · receptions · anytime_td.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / limit / anyOf
      Removed value: -[
-  {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "string"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / limit / type
      Added value: +[
+  "number",
+  "string",
+  "null"
+]
    • removedInput schema / properties / minEdge / anyOf
      Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "string"
-  }
-]
    • addedInput schema / properties / minEdge / type
      Added value: +[
+  "number",
+  "string"
+]
  2. Changed4 schema fields changed
    • addedInput schema / properties / propType / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "enum": [
+      "pass_yds",
+      "pass_tds",
+      "rush_yds",
+      "rec_yds",
+      "receptions",
+      "anytime_td"
+    ],
+    "type": "string"
+  }
+]
    • changedInput schema / properties / propType / description
      Previous value: -"Optional filter by prop type: pass_yds, pass_tds, rush_yds, rec_yds, receptions, anytime_td."New value: +"Optional filter by prop type. One of: pass_yds · pass_tds · rush_yds · rec_yds · receptions · anytime_td."
    • removedInput schema / properties / propType / enum
      Removed value: -[
-  "pass_yds",
-  "pass_tds",
-  "rush_yds",
-  "rec_yds",
-  "receptions",
-  "anytime_td"
-]
    • removedInput schema / properties / propType / type
      Removed value: -"string"
  3. Changed6 schema fields changed
    • addedInput schema / properties / limit / anyOf
      Added value: +[
+  {
+    "anyOf": [
+      {
+        "type": "number"
+      },
+      {
+        "type": "string"
+      }
+    ]
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / limit / default
      Removed value: -10
    • changedInput schema / properties / limit / description
      Previous value: -"Max rows (default 10)."New value: +"Max rows (default 10). Values above 25 are clamped to 25."
    • removedInput schema / properties / limit / maximum
      Removed value: -25
    • removedInput schema / properties / limit / minimum
      Removed value: -1
    • removedInput schema / properties / limit / type
      Removed value: -"integer"
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: the exact shape of returned rows (including 'WATCH rows labelled'), the temporal constraint ('Live in season'), and the auth requirement (Pro, sign in with PredictionMarketsPicks or a Pro API key).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Compact and front-loaded: the usage trigger leads, then the return shape, then the availability and auth caveats. No sentence is filler, and the field enumeration packs useful detail into a short span.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 returned fields, and it covers auth and season availability, which are the real gating concerns for a live prop tool. For a zero-required, three-parameter tool with full schema coverage and annotations, nothing essential is 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 coverage is 100%, so limit, minEdge, and propType are already fully documented in the schema. The description hints at prop-type filtering via 'receiving yards prop value' but adds no syntax, defaults, or clamping detail beyond what the schema provides, so the 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 a specific verb+resource: it compares 'our projection vs the Kalshi

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?

Front-loads concrete trigger queries ('best NFL props today', 'receiving yards prop value'), giving clear context for when to reach for it. There is no explicit exclusion or routing to alternatives such as nfl_prop_board, so it falls short of a full when/when-not treatment.

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

All Prediction Markets Quant 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