graph-polymarket-mcp

Overview Schema Source Related Servers Discussions Admin

get_oi_history

Retrieve hourly open interest snapshots for any Polymarket market using its conditionId, enabling analysis and charting of OI trends over time.

Instructions

Get hourly open interest snapshots for a specific Polymarket market. Use this to chart OI trends over time. The conditionId can be obtained from get_market_open_interest or the main subgraph.

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": {
      "conditionId": "<conditionId>"
    },
    "name": "get_oi_history"
  }
}

Input Schema

Name	Required	Description	Default
`first`	No	Number of hourly snapshots to return (default 168 = 1 week)
`conditionId`	Yes	The conditionId (hex string) of the market
`orderDirection`	No	Sort direction by timestamp	desc

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 3, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the hourly cadence, the market-specific scope, and the time-series nature. It implicitly indicates a read-only operation ('Get') but does not explicitly state safety, permissions, or return behavior beyond 'snapshots.'

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?

The description is three sentences, each earning its place. It front-loads the core purpose, adds a use case, and provides a parameter hint. No fluff or redundancy.

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?

Given the tool's moderate complexity (3 params, no output schema), the description covers the essential purpose and usage. It could be more explicit about the exact return fields, but 'hourly open interest snapshots' already implies the structure. The schema fills in parameter details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds value by telling the user how to obtain conditionId (from get_market_open_interest or the main subgraph), which enriches the required parameter's meaning beyond the schema.

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 starts with 'Get hourly open interest snapshots for a specific Polymarket market,' which clearly states the verb and resource. It distinguishes itself from siblings like get_market_open_interest (current OI) by emphasizing 'hourly' and 'over time,' and from query_subgraph by being a dedicated endpoint.

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?

It explicitly says 'Use this to chart OI trends over time,' providing a clear use case. It also mentions that conditionId can be obtained from get_market_open_interest, which helps navigate the workflow. However, it does not explicitly say when not to use it or name alternatives.

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