Skip to main content
Glama
Sign In

Vike Data API

by io.vike
OverviewDiscussionsAdmin

Polymarket Settlements Bulk

polymarket_settlements_bulk
Read-onlyIdempotent

On-chain resolutions of MANY Polymarket markets in one call, oldest resolution first, paged: the list form of polymarket_settlement (same row fields), for 'which markets resolved in this window', 'every settled BTC 5-minute market' or a backtest set. from_ms is inclusive and to_ms exclusive (epoch ms, on resolution time); slug_prefix (lowercase letters, digits and -, e.g. btc-updown-5m-) keeps one family of markets. Returns {settlements, has_more, next_cursor}; while has_more is true pass next_cursor back as cursor for the next page. Only markets the chain resolved appear: a cancelled or voided market with no on-chain resolution is not here. Pages are rebuilt every 5 minutes, so a market that resolved in the last 5 minutes may not be listed yet; polymarket_settlement is always current.

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows per page (default 100, max 5000).
to_msNoResolution time, epoch ms, exclusive; must be greater than from_ms. Omit for no upper bound.
cursorNoThe previous page's next_cursor.
from_msNoResolution time, epoch ms, inclusive. Omit for the first resolution.
slug_prefixNoOnly markets whose slug starts with this, e.g. `btc-updown-5m-`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Rows per page (default 100, max 500)."New value: +"Rows per page (default 100, max 5000)."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real behavioral context beyond them: oldest-first ordering, page rebuild cadence and the resulting staleness window, and the exclusion of cancelled/voided markets with no on-chain resolution.

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-loaded with purpose and sibling relationship, then parameters, then return shape and caveats. Dense but nearly every clause carries information; the single long paragraph is slightly harder to scan than a structured layout would be.

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

Completeness5/5

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

No output schema exists, yet the description documents the return shape ({settlements, has_more, next_cursor}) and the pagination protocol, plus the staleness caveat and the cancelled-market exclusion — everything needed to call and iterate correctly.

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 the baseline is 3, but the description adds value by restating the inclusive/exclusive boundary semantics, giving a concrete slug_prefix example ('btc-updown-5m-') and explaining the cursor loop ('while has_more is true pass next_cursor back as cursor').

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?

States a specific verb and resource ('On-chain resolutions of MANY Polymarket markets in one call') and explicitly positions itself as 'the list form of polymarket_settlement (same row fields)', so the agent can distinguish it from the single-market sibling without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete use cases ('which markets resolved in this window', 'every settled BTC 5-minute market', backtest sets) and an explicit routing rule: for the most recent 5 minutes use polymarket_settlement because it is always current while these pages are rebuilt every 5 minutes.

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 toolsInspect
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.

Resources