Skip to main content
Glama
Sign In

Prediction Markets Quant

by com.predictionmarketspicks
OverviewDiscussionsAdmin

NBA Prop Price Board (Kalshi vs the books)

nba_prop_board
Read-only

Use for "where is LeBron's points line cheapest tonight". Every Kalshi NBA player-prop strike (points, rebounds, assists, threes) beside DraftKings, FanDuel, BetRivers, Fanatics, ESPN, Novig and ProphetX at the same strike: the cheapest venue per side, Kalshi fee included. Market prices only, no model.

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": "nba_prop_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameNoTwo teams, e.g. "BOS @ DET".
teamNoTeam code or name (LAL, Lakers).
limitNoMax rows (default 15; 4 when the call has no arguments).
playerNoPlayer name (partial).
statTypeNoOptional stat. One of: pts · reb · ast · threes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max rows (default 15)."New value: +"Max rows (default 15; 4 when the call has no arguments)."
  2. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / limit / description
      Previous value: -"Max rows (default 15). Values above 50 are clamped to 50."New value: +"Max rows (default 15)."
  3. Changed2 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"
+]
  4. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the comparison is fee-inclusive for Kalshi and returns only one cheapest venue per side, not a full book-by-book table. It does not say whether prices are live or cached, nor anything about latency or coverage limits, which matters for a price board.

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?

Two dense sentences with zero filler: the use-case question is front-loaded, followed by what is compared and the fee caveat. Nothing repeats the schema or annotations.

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 more burden, and it does convey the core shape of the result: strikes across four stat types with book quotes and a cheapest-venue-per-side summary. What is missing is a hint at ordering/freshness of the returned rows, which an agent would want when deciding how many rows to request.

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 all five optional filters are already documented, and the description only restates the stat categories (points/rebounds/assists/threes) that statType already lists. The phrase "at the same strike" hints at matching semantics but adds no guidance on combining game/team/player filters or on limit behavior.

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 the exact resource (every Kalshi NBA player-prop strike — points, rebounds, assists, threes) and what is produced (a line-by-line comparison against eight named books with the cheapest venue per side). That scope is clearly distinct from siblings like nba_game_board or calculate_ev, though no sibling is named explicitly to sharpen the contrast.

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?

The opening quote, "where is LeBron's points line cheapest tonight," gives a concrete triggering question, and "Market prices only, no model" implicitly excludes pricing/EV work that belongs to calculate_ev. There is no explicit when-not clause or named alternative, so it stops short of a 5.

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