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 for the Bitcoin cycle feed). Age matters: these are cached reads, not live queries.

Schema Changelog

Changes observed during successful MCP inspections.

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 declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds useful selection behavior — upcoming dated events and moving odds — but does not detail sorting, time horizon, or data staleness. This is acceptable for a simple read operation but only moderately transparent.

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?

One sentence front-loads the resource and filter, then states the tool's purpose. Every word earns its place with no redundant filler or repetition of schema or annotation information.

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?

For a read-only, one-parameter endpoint with an output schema and full annotation coverage, the description provides enough context to invoke the tool correctly. The only notable gap is the lack of explicit differentiation from closely related prediction-market sibling tools, but this is not critical for basic invocation.

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% for the single limit parameter, including default and range, so the schema carries the parameter semantics. The description adds no parameter-specific detail, which is fine under the baseline-3 rule.

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?

The description clearly identifies the resource ('upcoming dated events on Polymarket') and the selection criterion ('odds are moving'), so an agent can tell what data the tool returns. It lacks an explicit verb like 'list' or 'return', but the meaning is unambiguous and distinct from sibling tools focused on yields, whales, or broad market analysis.

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 description implies usage when an agent wants near-term, narrative-moving catalysts, but it does not explicitly state when to use this over siblings such as get_prediction_market_yields or analyze_prediction_markets. No exclusions or decision rules are provided.

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.