Vike Data API

Polymarket Markets

polymarket_markets

Read-onlyIdempotent

Polymarket markets, by view. trending (default): top prediction-market events ranked by 24h volume. Returns market title, slug, category, current Yes/No mid quotes, 24h volume, and end_date. Filter by category (Crypto | Sports | Politics | Pop-Culture | Tech | all). Use for 'what's hot on Polymarket' or 'top crypto prediction markets'. search: the recorded markets whose slug contains query (case-insensitive), optionally only active or only closed ones, newest end_date first, paged with limit and offset; rows {active, closed, condition_id, end_date (epoch), neg_risk, slug, tick_size, token_ids}, active / closed derived from the on-chain resolution and Polymarket's own flag (a filter on them is the slower read). market: one market by condition_id in that row shape, a list of 0 or 1 rows, from the recorded markets or else Polymarket's full catalogue (source says which; an unknown id is []). Same data as GET /v1/polymarket/markets and /markets/{condition_id}.

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": "polymarket_markets"
  }
}

Input Schema

Name	Required	Description	Default
`view`	No	`trending` (default): top by 24h volume; `search`: filter the recorded markets; `market`: one market by condition_id.	trending
`limit`	No	Max markets: `trending` default 10, max 30; `search` default 50, max 100 (a larger value is clamped).
`query`	No	`search` only: case-insensitive substring of the market slug.
`active`	No	`search` only: true = only active markets, false = only closed ones; omit for all. Not together with `closed`.
`closed`	No	`search` only: the complement of `active` (true = only closed). Not together with `active`.
`offset`	No	`search` only: rows to skip, 0 to 10000 (default 0); above 10000 is refused.
`category`	No	`trending` only: category filter (default all)
`condition_id`	No	`market` only, required there: the 0x-prefixed condition id.

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedNov 2, 2026

addedInput schema / properties / active

Added value: +{
+  "description": "`search` only: true = only active markets, false = only closed ones; omit for all. Not together with `closed`.",
+  "type": [
+    "boolean",
+    "string"
+  ]
+}

removedInput schema / properties / category / default
```
Removed value: -"all"
```

changedInput schema / properties / category / description

Previous value: -"Category filter (default all)"New value: +"`trending` only: category filter (default all)"

addedInput schema / properties / closed

Added value: +{
+  "description": "`search` only: the complement of `active` (true = only closed). Not together with `active`.",
+  "type": [
+    "boolean",
+    "string"
+  ]
+}

addedInput schema / properties / condition_id

Added value: +{
+  "description": "`market` only, required there: the 0x-prefixed condition id.",
+  "type": "string"
+}

removedInput schema / properties / limit / default
```
Removed value: -10
```

changedInput schema / properties / limit / description

Previous value: -"Max markets (default 10, max 30)"New value: +"Max markets: `trending` default 10, max 30; `search` default 50, max 100 (a larger value is clamped)."

addedInput schema / properties / offset

Added value: +{
+  "description": "`search` only: rows to skip, 0 to 10000 (default 0); above 10000 is refused.",
+  "type": [
+    "integer",
+    "string"
+  ]
+}

addedInput schema / properties / query

Added value: +{
+  "description": "`search` only: case-insensitive substring of the market slug.",
+  "type": "string"
+}

addedInput schema / properties / view

Added value: +{
+  "default": "trending",
+  "description": "`trending` (default): top by 24h volume; `search`: filter the recorded markets; `market`: one market by condition_id.",
+  "enum": [
+    "trending",
+    "search",
+    "market"
+  ],
+  "type": "string"
+}

First observedOct 25, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive, and the description adds real behavioral context beyond them: an `active`/`closed` filter is 'the slower read', an unknown condition_id yields `[]`, offsets above 10000 are refused, oversized limits are clamped, and `source` reveals which catalogue answered. It doesn't mention rate limits or result freshness, so not a 5.

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?

Front-loads the view dispatch in the first clause and keeps everything in one dense paragraph with no filler. It is long and somewhat run-on in the `search` and `market` segments, but each clause carries information an agent needs for one of three distinct modes.

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 no output schema, the description carries the return-shape burden and does it well: it names the row fields for both the trending and search/market shapes and specifies ordering (newest end_date first) and paging. The only real gap is the missing boundary against the other polymarket_* market tools.

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 the baseline is 3. The description does add genuine value the schema lacks — the enumerated category values (Crypto | Sports | Politics | Pop-Culture | Tech | all) and the row field list — but most parameter semantics (defaults, clamping, mutual exclusion) are already in the schema text, so it is not purely additive.

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 resource and enumerates the three views with concrete behavior for each (trending = top events by 24h volume, search = slug substring match, market = single lookup by condition_id). An agent knows exactly what it gets. It stops short of distinguishing this from the near-named sibling polymarket_market_detail, which also returns a single market.

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?

Gives concrete trigger phrases ('what's hot on Polymarket', 'top crypto prediction markets') and per-view preconditions (search-only params, market requires condition_id). However, it never says when to prefer polymarket_market_detail, polymarket_market_stats, or the generic `search` tool over this one — the most likely routing confusion given the sibling list.

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

All Vike Data API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.