Skip to main content
Glama

DepthFeed

by com.depthfeed

polymarket_get_snapshots

Read-only

Historical order-book snapshots (time series) for one Polymarket market. Use interval to downsample and include_orderbook for the full ladder. History depth is gated by plan.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinNoCrypto asset. Keyless/demo and Free plans are BTC-only; all 7 require a paid plan.btc
limitNoPage size (1–1000).
cursorNoOpaque pagination cursor from a previous response's pagination.next_cursor.
end_timeNoEnd of time as ms-epoch or ISO-8601. History is clamped to your plan's window.
intervalNoDownsample bucket, e.g. 1m, 5m, 1h — one snapshot per bucket.
market_idYesMarket id from polymarket_search_markets.
start_timeNoStart of time as ms-epoch or ISO-8601. History is clamped to your plan's window.
include_orderbookNoInclude the full bid/ask ladder per snapshot (default top-of-book).

TDQS

A3.5/5.0
Behavior4/5

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

Description adds behavioral context beyond annotations: 'History depth is gated by plan' informs agents of access limitations. Annotations already declare readOnlyHint=true, so the description adds meaningful behavioral detail without contradiction.

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?

Concise two-sentence description, front-loaded with core purpose, followed by actionable usage hints. No redundant or extraneous content.

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?

Covers basic purpose and key parameters (interval, include_orderbook) but lacks return value description and does not quantify plan gating. With no output schema, description could be more complete, but it provides adequate context for an agent familiar with order-book snapshot concepts.

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?

Input schema has 100% description coverage, so description does not need to explain parameters. The description adds no new semantic information beyond the schema; it merely reiterates usage of interval and include_orderbook. Baseline score of 3 is appropriate.

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?

Clearly states it provides historical order-book snapshots for one Polymarket market, specifying 'time series' and mentioning interval and include_orderbook. Distinguishes from siblings by naming 'Polymarket' and focusing on one market, but does not explicitly differentiate from other get_snapshots tools.

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?

Provides internal usage tips (use interval to downsample, include_orderbook for full ladder) but no guidance on when to use this tool vs alternatives like polymarket_get_market or other providers' snapshots. Lacks explicit when-to-use or when-not-to-use context.

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

All DepthFeed toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool has a distinct purpose, clearly separated by venue prefix (kalshi_, limitless_, polymarket_) and action (get_orderbook, get_snapshots, search_markets). The screener and whoami tools are unique and not overlapping with any other tool.

Naming Consistency4/5

Most tools follow the venue_verb_noun pattern (e.g., kalshi_get_orderbook, polymarket_get_snapshots). However, polymarket_all_markets uses 'all' instead of a verb, and screener/whoami deviate entirely from the pattern, causing minor inconsistency.

Tool Count5/5

With 12 tools covering three venues plus cross-venue and session info, the count is well-scoped. Each tool serves a clear role without unnecessary bloat or deficiency.

Completeness4/5

The tool surface covers the core data retrieval operations (orderbook, snapshots, search, single market) for all venues. Missing are update/delete operations but those are outside the data provider scope. A minor gap is the lack of a dedicated 'get_market' for Kalshi and Limitless, though search_markets provides similar info.

Resources