Skip to main content
Glama

DepthFeed

by com.depthfeed

polymarket_search_markets

Read-only

List Polymarket up/down crypto prediction markets for a coin. Returns market id, slug, window, status and timing. Use the returned id/slug with polymarket_get_market or polymarket_get_snapshots.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinNoCrypto asset. Keyless/demo and Free plans are BTC-only; all 7 require a paid plan.btc
typeNoFilter by market window/type, e.g. 5m, 15m, 1h, 4h, 24h.
limitNoPage size (1–100).
cursorNoOpaque pagination cursor from a previous response's pagination.next_cursor.
end_timeNoFilter: markets active at/before this time as ms-epoch or ISO-8601. History is clamped to your plan's window.
resolvedNotrue → only resolved markets, false → only active.
start_timeNoFilter: markets active at/after this time as ms-epoch or ISO-8601. History is clamped to your plan's window.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint. The description adds behavioral context about returned fields and plan limitations (e.g., coin parameter restrictions). No contradictions.

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 concise sentences front-loading purpose and return values, then usage guidance. No extraneous words.

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?

With 7 parameters and no output schema, the description explains return fields and usage, but could mention pagination or filtering via cursor/limit. Still adequate given schema cover.

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 baseline is 3. The tool description does not add significant parameter meaning beyond the schema; the extra plan info is already in the schema description.

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 clearly states it lists Polymarket up/down crypto prediction markets for a coin, specifies returned fields (market id, slug, window, status, timing), and distinguishes from sibling tools by directing usage of returned ids with polymarket_get_market or polymarket_get_snapshots.

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?

Explicitly says to use returned id/slug with two other tools, indicating a workflow. Does not provide exclusions or when-not-to-use, but gives clear context for downstream usage.

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