Skip to main content
Glama

Enclave402

by com.enclave402
OverviewDiscussionsAdmin

Polymarket signal with derived edge: 1h/6h probability deltas, realized volatility and whale flow from the trade tape.

get_market_signal
Read-onlyIdempotent

Polymarket signal plus fields the free listing does not have: 1h and 6h probability deltas, 24h realized volatility, and whale flow from the trade tape (net YES notional, largest print, whale count, flow label). Plus prices, bid/ask, spread, 24h change, momentum, volume, liquidity. MUST be invoked when an agent needs where a market is MOVING, not just where it is. Do NOT use for spot prices or order execution. Settles $0.010 USDC on Base; no charge on failure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugNoOptional Polymarket market slug for one specific market. Omit to receive the top markets by 24h volume.
limitNoNumber of top markets to return when slug is omitted.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
tsNoResponse timestamp, UNIX milliseconds
asOfNoISO-8601 timestamp the data was fetched
queryNoEcho of the resolved query (slug, or top/orderBy)
sourceNoUpstream data providers
marketsNoNormalized market rows
settledNotrue when an x402 payment settled for this response (false on free-quota or dry-run)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / source / description
      Previous value: -"Upstream data provider"New value: +"Upstream data providers"
  2. Changed1 schema field changed
    • 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"
+}
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds valuable behavioral context beyond annotations by disclosing the settlement cost of $0.010 USDC on Base and that there is no charge on failure, which is critical for an agent deciding to invoke the tool.

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 well-structured: it front-loads the core value proposition, lists the differentiating fields, states usage criteria and exclusions, and ends with cost and failure behavior. Every sentence earns its place, and the use of a colon-delimited field list makes the dense information easy to scan.

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?

Given the output schema and annotations, the description is nearly complete. It covers use cases, exclusions, cost, and key return fields. It does not mention rate limits or latency, but those are not essential for correct invocation, and the settlement/failure disclosure is a strong addition for practical decision-making.

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?

The input schema has 100% description coverage for both parameters (slug and limit), so the schema already explains their meaning and constraints. The description does not add extra parameter-level context beyond what the schema provides, so a baseline score of 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 states a specific verb and resource: 'get_market_signal' returns Polymarket signal data with derived fields such as probability deltas, realized volatility, and whale flow. It clearly distinguishes this tool from alternatives by emphasizing it answers where a market is MOVING, not just where it is, which separates it from the sibling get_market_verdict and other listing tools.

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?

The description explicitly says 'MUST be invoked when an agent needs where a market is MOVING, not just where it is' and 'Do NOT use for spot prices or order execution.' This gives the agent clear selection criteria and exclusions, leaving no ambiguity about when to use this tool versus alternatives.

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

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