Skip to main content
Glama
Polymarket MCP Server

Polymarket MCP Server

by yashhsm

get_open_interest

Retrieve open interest for Polymarket markets by condition IDs or event ID, helping assess liquidity and trader participation.

Instructions

Get open interest for Polymarket markets

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

Input Schema

NameRequiredDescriptionDefault
marketNoCondition IDs
eventIdNoEvent ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden and falls well short. It does not say whether open interest is returned per market or aggregated, what units/currency it uses, or what happens when both optional filters are omitted. For a read tool with zero annotation coverage, this leaves the agent guessing about output shape and semantics.

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?

A single front-loaded sentence with no wasted words. It is efficient, though the extreme brevity borders on under-specification rather than disciplined conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description needed to explain return shape, units, and the both-params-optional behavior, and it does none of these. It is inadequate for a two-param tool where every parameter is optional.

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 100%, so 'market' (condition IDs) and 'eventId' are documented in the schema itself. The description adds nothing about their interaction — notably whether the array and eventId are mutually exclusive, combinable, or how the zero-required-parameter case behaves — so it stays at the baseline.

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 verb and resource: retrieve open interest for Polymarket markets. The metric is distinct from siblings like get_live_volume or get_top_holders, but the description does not explicitly differentiate itself or name any alternative.

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 guidance on when to use this tool versus filtering elsewhere, and no mention of prerequisites or exclusions. The agent must infer usage entirely from the one-line purpose statement.

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