Skip to main content
Glama
Sign In

Vike Data API

by io.vike
OverviewDiscussionsAdmin

Polymarket Settlement

polymarket_settlement
Read-onlyIdempotent

On-chain resolution of ONE Polymarket market, keyed by its condition_id (the market's 0x... hex id from polymarket_markets or polymarket_market_detail; an outcome token id matches nothing here). Returns [] or one row {condition_id, slug, question, outcomes, winning_index, winning_outcome, winning_token_id, token_ids, payouts, resolved_block, resolved_ts_ms (epoch ms), market_known}. market_known false means the market list has no row for it: slug, question, outcomes, token_ids, winning_outcome and winning_token_id are then empty, the on-chain fields still exact. [] means the chain has not resolved this condition, NOT that the market is open: a market can be cancelled or voided with no on-chain resolution, so read polymarket_market_detail for the market's own status.

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": {
      "condition_id": "<condition_id>"
    },
    "name": "polymarket_settlement"
  }
}

Input Schema

NameRequiredDescriptionDefault
condition_idYesRequired. The market's condition id (0x-prefixed hex).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description goes well beyond them: it describes the exact result cardinality ([] or one row), enumerates the returned fields, explains the market_known=false degraded mode and which fields go empty versus which on-chain fields stay exact. It also flags the critical interpretation trap around empty results, which no annotation covers.

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?

Purpose is front-loaded in the first clause and every subsequent sentence carries load-bearing semantics (return shape, empty-result meaning, fallback tool). It is a dense single paragraph with heavy parentheticals, which slightly hurts scanability for a rich description of this length.

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?

With no output schema, the description takes on the full burden of explaining return values and does so thoroughly, including field list, units (resolved_ts_ms epoch ms), and the market_known degraded case. Nothing an agent needs to call it correctly or interpret the result is missing.

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 genuine meaning: the id is a 0x hex condition id sourced from polymarket_markets/polymarket_market_detail, and outcome token ids are explicitly rejected. That disambiguation is not present in the schema text.

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 resolution of ONE Polymarket market') and emphasizes singularity, which separates it from the settlements_bulk sibling without naming it. It also pre-empts a likely confusion by stating that an outcome token id 'matches nothing here', so an agent can identify the correct key type from the text alone.

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?

Clear guidance on where the condition_id comes from (polymarket_markets or polymarket_market_detail) and an explicit corrective for the ambiguous empty case: '[] means the chain has not resolved this condition, NOT that the market is open... read polymarket_market_detail for the market's own status.' The one gap is that it never names polymarket_settlements_bulk as the alternative for querying many markets at once.

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