Skip to main content
Glama
Sign In

Prediction Markets Quant

by com.predictionmarketspicks
OverviewDiscussionsAdmin

2026 Race Odds — one Senate, governor or House race with every Kalshi leg

race_odds
Read-only

Use for "who wins the Kansas Senate race" and "Michigan governor odds". Live Kalshi odds for one 2026 Senate, governor or competitive House race, by state, code, slug or district ("TX-34"): every leg's price, volume and link, the seat holder and rating, forecaster bands, and the race page. Prices are never estimated.

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

Input Schema

NameRequiredDescriptionDefault
raceNoState name or code, a race slug (kansas-senate, michigan-governor, tx-34-house), or a House district (TX-34). Omit to list the races available.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / race / description
      Previous value: -"State name or code, a race slug (kansas-senate, michigan-governor, tx-34-house), or a House district (TX-34)."New value: +"State name or code, a race slug (kansas-senate, michigan-governor, tx-34-house), or a House district (TX-34). Omit to list the races available."
    • removedInput schema / properties / race / minLength
      Removed value: -1
    • removedInput schema / required
      Removed value: -[
-  "race"
-]
  2. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  3. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, openWorld, non-destructive), and the description adds genuinely new context: results are live (not cached/stale) and 'prices are never estimated', a data-provenance guarantee. It also enumerates the returned data, which matters since there is no output schema, but says nothing about rate limits or how often lines refresh.

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?

Two sentences, front-loaded with the user phrasings that should route here, then the scope. The opening sentence is a long run-on stacking query types, scope, input forms and return fields, so it is dense but essentially waste-free; the 'never estimated' line earns its place as a trust signal.

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?

For a single-parameter, zero-required-argument lookup with no output schema, the description supplies what the schema cannot: what a result contains (all Kalshi legs with price/volume/link, seat holder, rating, forecaster bands, race page) and that figures are live and non-estimated. Nothing needed to call it correctly 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% and the single parameter is already fully documented, so baseline 3 applies. The description restates the accepted input forms (state, code, slug, district like 'TX-34') but adds no format detail beyond the schema and never mentions the omit-to-list behavior that the schema itself carries.

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 concrete verb+resource: live Kalshi odds for a single 2026 Senate, governor or competitive House race, naming the exact scope ('one ... race') and the return contents (every leg's price, volume, link, seat holder, rating, forecaster bands, race page). An agent can distinguish this from senate_map (map-level) or market_pulse (broad) without opening any schema.

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?

Leads with explicit trigger queries ('who wins the Kansas Senate race', 'Michigan governor odds'), which is clear when-to-use guidance tied to real user phrasing. It stops short of naming when-not-to-use or pointing at the sibling alternatives (senate_map, market_pulse, best_price) for map-wide or price-comparison needs.

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