Liquid Agent

Polymarket price to beat (paid, $0.004)

polymarket_price_to_beat

Read-only

PAID over x402 inside this tool call ($0.004 USDC on Base, Polygon or Arc): the OFFICIAL Polymarket price to beat for the live BTC, ETH, SOL or XRP 5m/15m Up/Down window (matched to every decimal against Polymarket), the live Chainlink price and its distance, seconds left, token ids and market prices. Call it once without payment to get the x402 PaymentRequired; your x402 wallet signs it and you call again with the payment in _meta["x402/payment"]. Set free=true for one free answer per agent.

Input Schema

TableJSON Schema

Name	Required	Description
`free`	No	Use your one free call (per agent) instead of paying.
`start`	No	Optional unix start of a past window (official outcome).
`market`	Yes	Which market: <asset>-<timeframe>.

Output Schema

TableJSON Schema

Name	Required	Description
`_paid`	No	x402 receipt
`market`	No	Market, e.g. btc-5m
`tokens`	No	Up and Down token ids and market prices
`window`	No	Window start and end
`outcome`	No	Outcome of a past window
`chainlink`	No	Live Chainlink price and distance from the price to beat
`priceToBeat`	No	Official price to beat for the window
`secondsLeft`	No	Seconds left in the window

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "_paid": {
+      "additionalProperties": {},
+      "description": "x402 receipt",
+      "properties": {},
+      "type": "object"
+    },
+    "chainlink": {
+      "additionalProperties": {},
+      "description": "Live Chainlink price and distance from the price to beat",
+      "properties": {},
+      "type": "object"
+    },
+    "market": {
+      "description": "Market, e.g. btc-5m",
+      "type": "string"
+    },
+    "outcome": {
+      "description": "Outcome of a past window",
+      "type": "string"
+    },
+    "priceToBeat": {
+      "description": "Official price to beat for the window",
+      "type": "number"
+    },
+    "secondsLeft": {
+      "description": "Seconds left in the window",
+      "type": "number"
+    },
+    "tokens": {
+      "additionalProperties": {},
+      "description": "Up and Down token ids and market prices",
+      "properties": {},
+      "type": "object"
+    },
+    "window": {
+      "additionalProperties": {},
+      "description": "Window start and end",
+      "properties": {},
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

AddedSep 30, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only declare read-only/open-world/idempotent=false; the description adds substantial behavior an agent needs—exact cost ($0.004 USDC), accepted chains, the two-call payment handshake, and the one-free-answer-per-agent limit. This is real context beyond the structured fields.

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 the payoff and payment model, and every sentence carries usable information. The first sentence is dense and slightly run-on, but nothing is wasted.

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 a full enum in the schema, an output schema covering return values, and annotations covering the safety profile, the description supplies the only missing piece—the paid x402 invocation flow—leaving nothing an agent needs absent.

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% with the market enum fully enumerated, so the schema carries parameter meaning and the baseline is 3. The description's mention of assets/timeframes roughly mirrors the enum and adds no syntax detail on the optional 'start' parameter.

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 resource (official Polymarket price to beat) scoped to concrete assets (BTC/ETH/SOL/XRP) and timeframes (5m/15m Up/Down), plus the data it returns (Chainlink price, distance, seconds left, token ids). An agent can distinguish this from sibling data tools like stocks_signals or polymarket_prepare without opening the schema.

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 explicit procedural guidance: call once unpaid to receive the x402 PaymentRequired, sign with the x402 wallet, then re-call with payment in _meta['x402/payment'], or use free=true. It does not, however, position this against sibling tools (x402_check, polymarket_prepare) or state when-not to use it.

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

All Liquid Agent 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.