Skip to main content
Glama
predmarket-mcp

predmarket-mcp

get_price_history

Read-only

Retrieve YES price history for Kalshi or Polymarket prediction markets, with hourly points for up to 7 days and daily points for longer ranges up to 90 days.

Instructions

YES price history: hourly points up to 7 days, daily points beyond that (max 90 days).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "venue": "<venue>",
      "market_id": "<market_id>"
    },
    "name": "get_price_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoursNo
venueYes
market_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior the annotations cannot: resolution degrades from hourly to daily past 7 days, and the total window is capped at 90 days. It does not say whether exceeding 90 days is clamped or errors, which is the one missing edge case.

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?

A single dense sentence with no filler, and the most decision-relevant fact (granularity vs range) is front-loaded. It loses a point only because 'YES' is an unexplained shorthand that costs the reader a beat.

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?

An output schema exists, so return format needn't be described, and annotations cover read-only semantics. However, for a three-parameter tool at 0% schema coverage, leaving venue and market_id entirely undefined and the over-90-days behavior unknown leaves real gaps.

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 0%, so the schema gives names and defaults only; the description partially compensates by explaining the effect of the hours value (hourly ≤7d, daily beyond, max 90d). It adds nothing about venue or market_id, including the expected ID format for market_id.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase 'YES price history' identifies the resource (price history for the YES outcome) plus the venue/market_id params make the target clear, but there is no verb and no explicit statement that it returns a time series. 'YES' is unexplained shorthand, and nothing distinguishes it from get_recent_trades, the nearest sibling.

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 guidance on when to use this instead of get_recent_trades, get_orderbook, or get_market, and no prerequisites. The only contextual rule given is about data granularity, not tool selection.

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