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

mcp-server-polymarket

by tukorama
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Get Perps exchange statistics

get_perps_exchange_stats
Read-onlyIdempotent

Retrieve exchange-wide perpetual futures volume, trade counts, fees, and open interest over a window of up to 31 days, with optional start and end times.

Instructions

Exchange-wide volume, trades, fees and open interest over a window of up to 31 days.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_perps_exchange_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoISO 8601 time, e.g. 2026-11-01 or 2026-11-01T12:00:00Z, or epoch seconds.
startNoEmpty means 24 hours ago.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description contributes one genuinely new behavioral fact — the maximum 31-day window — but says nothing about aggregation granularity, timezone handling, or what happens if the window is exceeded, and an output schema already covers return 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?

A single front-loaded sentence that states scope first (Exchange-wide) and then the metrics and the window limit. No filler, no redundancy with the title beyond what is useful.

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?

With only two optional parameters, full schema coverage, annotations, and an output schema, the definition is close to sufficient. It still leaves open the aggregation granularity (single summary vs. per-day buckets) and the behavior when the requested range exceeds 31 days, both of which an agent would want before calling.

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%, with both start and end documented including the 'empty means 24 hours ago' default, so the baseline is 3. The description's 'window of up to 31 days' adds a constraint on the start/end pair that the schema does not state, which is a marginal but real gain.

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?

The description names the resource (exchange-wide perps statistics) and enumerates the specific metrics returned: volume, trades, fees, and open interest. 'Exchange-wide' implicitly distinguishes it from per-instrument siblings like get_perps_tickers or get_perps_book, but no sibling is named explicitly.

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 explicit guidance on when to choose this tool over alternatives such as get_open_interest or get_perps_tickers, and no stated prerequisites. The only usage-shaped information is the implicit 31-day window cap, which reads more as a constraint than a selection criterion.

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