Agent Einstein — Crypto & Market Intelligence

Prediction Market Yield Surface

get_prediction_market_yields

Read-onlyIdempotent

Near-certain Polymarket outcomes ranked by annualized return to resolution — the "cash-like yield" view of prediction markets.

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.
`totals`	No	Totals across the surface.
`trades`	No	Redemption-arb tickets — near-certain outcomes still trading below $1.
`wallets`	No	Wallets taking those tickets.
`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.
`truncated`	No	Present only when a list was cut to `limit`.
`priceFloor`	No	Entry price a ticket had to clear, 0-1.
`lookbackHours`	No	Window scanned.
`minCollateralUsd`	No	USD size a ticket had to clear.

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"
+    },
+    "lookbackHours": {
+      "description": "Window scanned."
+    },
+    "minCollateralUsd": {
+      "description": "USD size a ticket had to clear."
+    },
+    "priceFloor": {
+      "description": "Entry price a ticket had to clear, 0-1."
+    },
+    "reason": {
+      "description": "Why the payload is absent, when `available` is false.",
+      "type": "string"
+    },
+    "stale": {
+      "description": "True when the snapshot is past its refresh interval."
+    },
+    "totals": {
+      "additionalProperties": true,
+      "description": "Totals across the surface.",
+      "properties": {
+        "collateralUsd": {
+          "description": "USD collateral behind them."
+        },
+        "spreadUsd": {
+          "description": "USD spread to resolution."
+        },
+        "trades": {
+          "description": "Tickets counted."
+        }
+      }
+    },
+    "trades": {
+      "description": "Redemption-arb tickets — near-certain outcomes still trading below $1.",
+      "items": {},
+      "type": "array"
+    },
+    "truncated": {
+      "additionalProperties": true,
+      "description": "Present only when a list was cut to `limit`.",
+      "properties": {
+        "limit": {
+          "description": "The cap that was applied.",
+          "type": "number"
+        },
+        "originalLengths": {
+          "additionalProperties": true,
+          "description": "Field name → its full length before the cut."
+        }
+      }
+    },
+    "wallets": {
+      "description": "Wallets taking those tickets.",
+      "items": {},
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

AddedAug 17, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already convey read-only, idempotent, non-destructive behavior, so the bar is lower here. The description adds genuinely useful behavior beyond those annotations: it filters to near-certain outcomes and ranks by annualized return to resolution, which is the tool's core selection logic.

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 dense sentence that front-loads the key selection and ranking criteria. Every phrase earns its place, and there is no redundant restatement of the title or annotations.

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 low parameter count, rich annotations, and presence of an output schema, the description is sufficient for correct invocation. The only minor gap is not specifying the ranking direction explicitly, but 'ranked by annualized return to resolution' strongly implies descending yield.

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?

There is only one parameter, limit, and the input schema provides full documentation with default and range (1-25). Per the baseline for high schema coverage, the description does not need to add parameter-level detail.

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 outcomes), a specific filter (near-certain), and a specific ordering (annualized return to resolution). The 'cash-like yield' framing clearly separates it from siblings like get_prediction_market_catalysts or analyze_prediction_markets.

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 this tool is for viewing prediction markets as a cash-like yield surface, so an agent could infer when to call it. However, it does not explicitly state when to prefer this over sibling tools such as analyze_prediction_markets or get_prediction_market_catalysts, nor does it name any exclusions.

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.