Enclave402

Live Polymarket prediction-market signal (prices, spread, 24h change, volume, liquidity).

get_market_signal

Read-onlyIdempotent

Live Polymarket prediction-market signal: outcome prices (implied probabilities), best bid/ask and spread, 24h change with a deterministic momentum label, 24h volume and liquidity. MUST be invoked when an agent needs the crowd-implied probability of a real-world event or the most-traded markets right now. Do NOT use for spot token prices, swap quotes or order execution; read-only. Settles $0.010 USDC via x402 on Base; no charge on failure; public receipts at /api/ledger.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	No	Optional Polymarket market slug for one specific market. Omit to receive the top markets by 24h volume.
`limit`	No	Number of top markets to return when slug is omitted.

Output Schema

TableJSON Schema

Name	Required	Description
`ts`	No	Response timestamp, UNIX milliseconds
`asOf`	No	ISO-8601 timestamp the data was fetched
`query`	No	Echo of the resolved query (slug, or top/orderBy)
`source`	No	Upstream data provider
`markets`	No	Normalized market rows
`settled`	No	true when an x402 payment settled for this response (false on free-quota or dry-run)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "asOf": {
+      "description": "ISO-8601 timestamp the data was fetched"
+    },
+    "markets": {
+      "description": "Normalized market rows"
+    },
+    "query": {
+      "description": "Echo of the resolved query (slug, or top/orderBy)"
+    },
+    "settled": {
+      "description": "true when an x402 payment settled for this response (false on free-quota or dry-run)"
+    },
+    "source": {
+      "description": "Upstream data provider"
+    },
+    "ts": {
+      "description": "Response timestamp, UNIX milliseconds"
+    }
+  },
+  "type": "object"
+}

First observedSep 17, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare the tool read-only, idempotent, and non-destructive. The description adds genuinely new behavioral context: it settles $0.010 USDC via x402 on Base, charges nothing on failure, exposes public receipts at /api/ledger, and mentions a deterministic momentum label. This goes well beyond the structured annotations and contains no contradiction.

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?

The description is compact and front-loaded with the core payload, then quickly moves to usage triggers, exclusions, and billing behavior. Every sentence adds distinct information, and there is no filler or repetition of the annotations without value.

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?

Given the tool is a read-only market-data lookup with an output schema and fully described parameters, the description is complete: it explains what the tool returns, when to use it, what not to use it for, cost, failure behavior, and where receipts live. No meaningful gap remains for an agent to call it correctly.

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 the parameters are already fully documented: slug selects one market and limit caps top-market results when slug is omitted. The description doesn't add much parameter-level detail, but it doesn't need to because the schema carries that load. Baseline 3 is appropriate.

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 names a specific resource (Polymarket prediction-market signal) and the exact data it returns: outcome prices, bid/ask/spread, 24h change with momentum label, volume, and liquidity. It also clearly distinguishes this from other tool purposes by explicitly saying it must be used for crowd-implied probabilities and must not be used for spot token prices or swap quotes.

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?

It gives explicit trigger conditions: use when an agent needs a crowd-implied probability of a real-world event or the most-traded markets right now. It also states negative usage constraints, such as not using it for spot token prices, swap quotes, or order execution, making the decision boundary unambiguous.

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

All Enclave402 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.

Resources

Need Help?