Skip to main content
Glama

get_prediction_market_history

Read-only

Read stored price changes for one Kalshi or Polymarket contract id from get_prediction_markets, newest first, last 14 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": {
      "id": "<id>"
    },
    "name": "get_prediction_market_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
limitNo
sourceNokalshi

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavior: data is 'stored' rather than live, results are ordered newest first, and coverage is capped at 14 days. It does not explain truncation behavior or what happens for an unknown id.

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?

A single dense sentence with zero filler, front-loading the action and following with scope, ordering, and window. Every clause adds information.

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?

Sufficient for a simple three-parameter read tool whose safety semantics are handled by annotations, and it describes the return content (price changes) even without an output schema. It could say more about how limit interacts with the 14-day window and what happens when the id yields no data.

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 description must carry parameter meaning, and it does partially: it identifies what 'id' is (a Kalshi/Polymarket contract id from get_prediction_markets) and why 'source' exists. The 'limit' parameter and its 1-200 range are never explained, leaving a clear gap.

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 specific verb ('Read stored price changes'), a precise resource (one contract id), the data provenance and window ('newest first, last 14 days'). It also distinguishes itself from the sibling get_prediction_markets by naming it as the source of valid ids.

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 prerequisite is explicit: the id must come from get_prediction_markets, and the source enum is implicitly tied to Kalshi or Polymarket. There is no explicit when-not guidance or mention of alternatives such as get_history, which keeps this at 4 rather than 5.

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.