Skip to main content
Glama

get_prediction_markets

Read-only

Read Kalshi or Polymarket player-prop contracts (best ask, dollars per $1 contract) with implied probability, American and decimal odds, the venue no-vig probability, matched BetRivers US-PA prices and edge versus the sportsbook no-vig probability. Available to every key. Edge is not a guaranteed profit; fees and fills are not modeled.

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

Input Schema

NameRequiredDescriptionDefault
statNo
limitNo
leagueNo
offsetNo
playerNo
sourceNokalshi

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-derivable behavior: access scope ('Available to every key') and explicit caveats that edge is not guaranteed profit and that fees and fills are not modeled — material for interpreting results. It omits pagination/rate-limit behavior, keeping it below a 5.

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 resource and the returned fields, followed by the caveat. The middle of the first sentence is a dense enumeration of measures, but each item is informative rather than filler, so the density is justified.

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

Completeness3/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 return values, and the annotations cover safety. However, for a six-parameter tool with 0% schema coverage, the absence of any parameter semantics (especially source, league, limit/offset) leaves a real gap an agent must guess at.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across six parameters, so the description carries the full burden and largely fails it: stat, player, league, limit and offset receive no explanation at all. The only implicit mapping is 'Kalshi or Polymarket' to the source enum and 'player-prop' hinting at player/stat, which is minimal compensation for five undocumented parameters including pagination controls.

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 gives a specific verb and resource: 'Read Kalshi or Polymarket player-prop contracts', and enumerates the returned measures (best ask, implied probability, odds formats, no-vig probability, sportsbook edge). That makes it distinguishable in substance from sportsbook-oriented siblings like get_player_props or get_novig_markets, though it never names an alternative explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use / when-not guidance and no reference to any sibling tool. The only access guidance is 'Available to every key', which tells the agent about authentication scope but not tool selection. An agent must infer from the sibling list which tool to pick for prediction-market versus sportsbook props.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.