Skip to main content
Glama

Fetches historical price points for a Polymarket outcome

pm_history
Read-only

Fetches historical price points for a Polymarket outcome token across standard intervals (1h, 6h, 1d, 1w, max) or with custom fidelity. Timestamps formatted in ISO. Maximum 1,000 points. Information only, not financial advice. Related tools on this server, for a different need: pm_orderbook when you need to fetch resting order book depth for a Polymarket outcome; pm_event when you need to fetch details for a single Polymarket event by slug. Price: $0.003 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "tokenId": "<tokenId>"
    },
    "name": "pm_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum data points to return (max 1000)
tokenIdYesOutcome CLOB token ID (numeric string)
fidelityNoMinutes between points, 1 to 1440 (e.g. 60 for hourly); default: Polymarket's own resolution for the interval
intervalNoTime interval: 1h, 6h, 1d, 1w, or max

Output Schema

NameRequiredDescriptionDefault
sourceNo
historyNo
tokenIdNo
intervalNo
checkedAtNo
truncatedNo
disclaimerNo
pointsCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / truncated
      Added value: +{}
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, yet the description adds material context they don't cover: a hard cap of 1,000 points, ISO timestamp formatting, and – most importantly – the paid-call model ($0.003 per successful call via x402 USDC, failed calls free), which is essential for an agent to reason about cost and repeated invocation. Gaps remain: no mention of pagination or how errors surface for an invalid tokenId.

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?

The purpose and interval scope are front-loaded in the first sentence, with cost and sibling routing in a clearly delimited trailing segment. The sentence "Information only, not financial advice" is disposable boilerplate, but the rest is dense and earns its space.

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?

Because an output schema exists, return values need not be explained, and the description covers the remaining agent-critical facts: the data cap, timestamp format, payment/auth model, and sibling alternatives. Only edge-case behavior (empty results, invalid token handling) is unaddressed, which is minor for a read-only historical fetch.

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% and all four parameters are documented in the schema, including enum-like interval values and the fidelity range, so the schema already carries the detail. The description echoes the interval set and the 1,000-point maximum but adds no parameter-level meaning beyond what is structured, making the 3 baseline appropriate.

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?

The description opens with a specific verb and resource ("Fetches historical price points for a Polymarket outcome token") and immediately narrows scope to standard intervals or custom fidelity. It also names the sibling tools (pm_orderbook for order book depth, pm_event for event details by slug) and the different need each serves, so an agent can discriminate 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?

Guidance is explicit on the alternatives side: pm_orderbook covers resting depth and pm_event covers event details, which cleanly routes the agent away from this tool for those needs. It stops short of stating exclusions for this tool itself (e.g., whether it covers resolved markets or how it differs from pm_trades/pm_resolved), leaving some context implicit.

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.

Resources