Skip to main content
Glama
mcp-server-polymarket

mcp-server-polymarket

Get Perps funding history

get_perps_funding_history
Read-onlyIdempotent

Retrieve settled perpetual-futures funding rates for an instrument, up to 100 records per call, to analyze funding costs; positive rates mean longs pay shorts.

Instructions

Settled funding rates of an instrument, up to 100 per call. Positive rates mean longs pay shorts.

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_funding_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoISO 8601 time, e.g. 2026-11-01 or 2026-11-01T12:00:00Z, or epoch seconds.
startNoISO 8601 time, e.g. 2026-11-01 or 2026-11-01T12:00:00Z, or epoch seconds.
instrument_idYesPerps instrument id, e.g. 1.

Output Schema

NameRequiredDescriptionDefault
noteNo
countNo
itemsNo
has_moreNo
next_cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior the annotations do not carry: only settled (not predicted) rates are returned, the 100-row per-call ceiling, and the meaning of positive values.

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, both load-bearing: the first fixes the resource, the row cap, and settlement scope; the second fixes the interpretation of the returned numbers. No filler.

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?

An output schema exists, so return shape need not be described, and read-only semantics come from annotations. The remaining gap is pagination and default time-window behavior when start/end are null, which matters for retrieving more than 100 rows but is not stated.

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%, so the ISO 8601 / epoch formats for start and end are already documented. The description adds nothing parameter-specific and is silent on what happens when start or end are omitted, which is the main semantic question for a time-windowed history call.

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 and scope: settled funding rates for a single perps instrument, capped at 100 rows per call, with the sign convention defined. That clearly separates it from candles/price history siblings, though it never names an alternative tool explicitly.

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

Usage Guidelines3/5

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

The sign convention sentence implies how to interpret results and the 100-row cap hints at batching, but there is no explicit guidance on when to choose this over get_perps_candles or get_price_history, and no mention of prerequisites such as needing a perps instrument id from list_perps_instruments.

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