Agent Einstein — Crypto & Market Intelligence

Prediction Market Catalyst Radar

get_prediction_market_catalysts

Read-onlyIdempotent

Upcoming dated events on Polymarket whose odds are moving — the catalysts most likely to move crypto or macro narratives next.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum rows to return (1-25).

Output Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Row cap applied to every list in this payload.
`stale`	No	True when the snapshot is past its refresh interval.
`reason`	No	Why the payload is absent, when `available` is false.
`matches`	No	Prediction markets whose odds moved against a dated catalyst.
`available`	No	False when this call has no data — a snapshot that is not warm yet, a domain switched off, or an argument that was rejected. NOT an error, and NOT a statement about the market.
`fetchedAt`	No	When the underlying snapshot was refreshed (epoch ms or ISO-8601). Age matters: these are cached reads, not live queries.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 29, 2026

changedOutput schema / properties / fetchedAt / description

Previous value: -"When the underlying snapshot was refreshed (epoch ms, or ISO-8601 for the Bitcoin cycle feed). Age matters: these are cached reads, not live queries."New value: +"When the underlying snapshot was refreshed (epoch ms or ISO-8601). Age matters: these are cached reads, not live queries."

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "available": {
+      "description": "False when this call has no data — a snapshot that is not warm yet, a domain switched off, or an argument that was rejected. NOT an error, and NOT a statement about the market.",
+      "type": "boolean"
+    },
+    "fetchedAt": {
+      "description": "When the underlying snapshot was refreshed (epoch ms, or ISO-8601 for the Bitcoin cycle feed). Age matters: these are cached reads, not live queries."
+    },
+    "limit": {
+      "description": "Row cap applied to every list in this payload.",
+      "type": "number"
+    },
+    "matches": {
+      "description": "Prediction markets whose odds moved against a dated catalyst.",
+      "items": {},
+      "type": "array"
+    },
+    "reason": {
+      "description": "Why the payload is absent, when `available` is false.",
+      "type": "string"
+    },
+    "stale": {
+      "description": "True when the snapshot is past its refresh interval."
+    }
+  },
+  "type": "object"
+}

AddedAug 17, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the description does not need to restate them. It adds useful sourcing and filtering context (Polymarket, dated/upcoming, odds-moving) but says nothing about ordering, freshness, or how 'moving' is quantified.

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?

A single front-loaded sentence that conveys resource, source, and selection criterion with zero waste. Nothing to trim.

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?

An output schema exists, so return-shape details are not needed in the description, and read-only annotations carry the safety profile. The description is sufficient for a simple one-param read tool, missing only explicit sibling routing.

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 single 'limit' parameter is fully documented in the schema (100% coverage), so the schema does the heavy lifting. The description adds no meaning about the parameter or default behavior, so the baseline 3 for high-coverage schemas applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names the resource and scope precisely — 'upcoming dated events on Polymarket whose odds are moving' — so an agent knows it returns moving-odds catalyst events rather than raw market lists or yields. It is clear but does not explicitly distinguish itself from close siblings like analyze_prediction_markets or get_prediction_market_yields.

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

Usage Guidelines3/5

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

The phrase 'most likely to move crypto or macro narratives next' implies when the tool is useful (narrative/theme radar), which is helpful framing. However, it offers no explicit when-to-use vs when-not or named alternatives, leaving selection between the three prediction-market siblings to inference.

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

All Agent Einstein — Crypto & Market Intelligence 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.