Prediction Markets Quant

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nfl_prop_edge"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max rows (default 10; 5 when the call has no arguments).
`minEdge`	No	Min absolute edge in pp (default 5).
`propType`	No	Optional 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.

Changed1 schema field changedNov 5, 2026

changedInput schema / properties / limit / description

Previous value: -"Max rows (default 10)."New value: +"Max rows (default 10; 5 when the call has no arguments)."

Changed3 schema fields changedOct 23, 2026

removedInput schema / $schema

Removed value: -"https://json-schema.org/draft/2020-12/schema"

changedInput schema / properties / limit / description

Previous value: -"Max rows (default 10). Values above 25 are clamped to 25."New value: +"Max rows (default 10)."

changedInput schema / properties / minEdge / description

Previous value: -"Min absolute edge in pp (default 5). Accepts a number or a numeric string (\"3\", \"3pp\", \"3%\")."New value: +"Min absolute edge in pp (default 5)."

Changed4 schema fields changedOct 15, 2026

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"
+]
```

Changed4 schema fields changedOct 6, 2026

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

Changed6 schema fields changedOct 1, 2026

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

First observedSep 6, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations only cover read-only/open-world, so the description carries the real burden and does add value: Pro authentication via PredictionMarketsPicks sign-in or an API key, seasonal availability, and the presence of WATCH-labelled rows. It still doesn't say what happens when unauthenticated (error vs empty result) or whether results are cached/live-refreshed, which are the remaining gaps.

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?

Trigger phrases come first, followed by output contents, then availability and auth, so the important information is front-loaded. The sentence-fragment style is dense but each clause carries information; no filler.

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 usefully enumerates the returned fields and flags WATCH rows, and it discloses the auth prerequisite and seasonality. For a read-only, three-optional-parameter tool that is nearly complete; only error/unauthenticated behavior is left unstated.

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 limit, minEdge and propType are already fully documented, and the description adds essentially no extra meaning — the 'receiving yards' phrasing is the only loose echo of propType. Baseline 3 applies since the schema does the heavy lifting.

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 states a concrete resource (NFL player prop projections compared against Kalshi 'X or more' lines) and concretely lists what each row contains: contract, YES/NO call, both prices, projection, and edge. That separates it well from generic siblings like nfl_prop_board, though it never names a sibling to make the distinction explicit.

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?

It gives two literal trigger phrases ('best NFL props today', 'receiving yards prop value') and the 'Live in season' availability cue, which is useful context. But there is no explicit when-not guidance and no pointer to nfl_prop_board or explain_prop as alternatives when the agent wants raw lines instead of edges.

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

NFL Player Prop Edge (model vs Kalshi)

Tool call template

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources