Skip to main content
Glama
Sign In
mcp-server-polymarket

mcp-server-polymarket

by tukorama
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Get Perps candles

get_perps_candles
Read-onlyIdempotent

Fetch historical OHLCV or mark-price candles for a perpetual futures instrument to analyze price movement and backtest strategies.

Instructions

Price candles for an instrument, oldest first. With kind=mark, close is the mark price at the end of each bucket.

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": {
      "instrument_id": "<instrument_id>"
    },
    "name": "get_perps_candles"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoISO 8601 time, e.g. 2026-11-01 or 2026-11-01T12:00:00Z, or epoch seconds.
kindNotrades: OHLCV of trades; mark: mark price.trades
countNoCandles when start is empty.
startNoEmpty looks back `count` intervals.
intervalNo1h
instrument_idYesPerps instrument id, e.g. 1.

Output Schema

NameRequiredDescriptionDefault
kindYes
moreNo
candlesYes
intervalYes
instrument_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and open-world behavior, so the safety profile is covered. The description adds genuinely new context: candles are returned oldest-first and `close` means the mark price when kind=mark. It stops there, saying nothing about bucket alignment, how start and end interact, or volume semantics.

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?

Two short sentences, front-loaded with the primary purpose and then a single qualifier about the mark kind. There is no filler and no restatement of the tool name.

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?

With a rich schema, an output schema, and strong annotations, the description only needs to add the interpretation an agent cannot get from structured fields, and it does that for mark-price closes. The remaining gap is the start/end/count interaction, which the schema largely covers.

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 83%, so the schema already documents start, end, count, interval, kind and instrument_id with examples. The description contributes one extra semantic link (kind=mark changes what `close` means) but adds nothing about how start, end and count combine, leaving the schema to carry the load.

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?

States a specific resource (price candles for an instrument) and adds the output ordering ('oldest first'), which is concrete enough to distinguish it from trade listings or book snapshots. It does not explicitly differentiate itself from the sibling get_price_history, so it stops short of a 5.

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 or when-not-to-use guidance, and no alternative tool is named. An agent must infer from the name alone whether this or get_price_history is the right call, and nothing explains how start/end/count combinations should be chosen.

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

Deploy Server

Other Tools