Agent Einstein — Crypto & Market Intelligence

Top Gainers and Losers

get_top_movers

Read-onlyIdempotent

The largest 24h movers across the major-cap crypto universe, gainers or losers, from a refreshed market snapshot.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`side`	No	Which end of the board to return.	gainers
`limit`	No	Maximum rows (1-25).

Output Schema

TableJSON Schema

Name	Required	Description
`side`	No	Which side was asked for — gainers or losers.
`limit`	No	Row cap applied to every list in this payload.
`stale`	No	True when the snapshot is past its refresh interval.
`errors`	No	Legs that failed. A partial answer says so here rather than reading as a quiet market.
`reason`	No	Why the payload is absent, when `available` is false.
`source`	No	Price source behind the cross-asset ranking.
`idSource`	No	Source of the asset identifiers.
`perChain`	No	Per-chain movers, keyed by chain.
`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.
`crossAsset`	No	Cross-asset ranking plus the universe/cohort sizes it was drawn from.
`perChainUnavailable`	No	True when the per-chain leg could not be read.

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"
+    },
+    "crossAsset": {
+      "additionalProperties": true,
+      "description": "Cross-asset ranking plus the universe/cohort sizes it was drawn from.",
+      "properties": {
+        "cohortSize": {
+          "description": "Assets in the ranked cohort."
+        },
+        "gainers": {
+          "description": "Top gainers.",
+          "items": {},
+          "type": "array"
+        },
+        "losers": {
+          "description": "Top losers.",
+          "items": {},
+          "type": "array"
+        },
+        "universeSize": {
+          "description": "Assets considered before filtering."
+        }
+      }
+    },
+    "errors": {
+      "description": "Legs that failed. A partial answer says so here rather than reading as a quiet market.",
+      "items": {
+        "description": "Error text."
+      },
+      "type": "array"
+    },
+    "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."
+    },
+    "idSource": {
+      "description": "Source of the asset identifiers."
+    },
+    "limit": {
+      "description": "Row cap applied to every list in this payload.",
+      "type": "number"
+    },
+    "perChain": {
+      "additionalProperties": true,
+      "description": "Per-chain movers, keyed by chain."
+    },
+    "perChainUnavailable": {
+      "description": "True when the per-chain leg could not be read."
+    },
+    "reason": {
+      "description": "Why the payload is absent, when `available` is false.",
+      "type": "string"
+    },
+    "side": {
+      "description": "Which side was asked for — gainers or losers."
+    },
+    "source": {
+      "description": "Price source behind the cross-asset ranking."
+    },
+    "stale": {
+      "description": "True when the snapshot is past its refresh interval."
+    }
+  },
+  "type": "object"
+}

AddedAug 17, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the trait 'refreshed market snapshot,' which signals that results are time-sensitive and drawn from a current data state. There is no contradiction with the annotations.

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 sentence that front-loads the core result ('largest 24h movers'), then adds scope and freshness. Every phrase earns its place, with no redundant filler or restatement of the title.

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 low-complexity, read-only retrieval tool with only two optional parameters and a full output schema, this description is nearly complete. It conveys the universe, timeframe, direction options, and freshness. Minor ambiguities remain, such as whether 'movers' means percentage change or absolute change and what 'major-cap' includes, but they are not blocking.

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%: both 'side' and 'limit' are documented in the schema with their defaults and constraints. The description does not need to add parameter meaning, and it mostly restates the 'gainers or losers' concept already captured by the enum.

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 identifies a specific resource: the largest 24h movers in the major-cap crypto universe, explicitly including gainers or losers. It lacks an imperative verb like 'list' or 'return', but the noun phrase and title make the tool's function clear. It is distinguishable from many siblings because it pinpoints a 24-hour movers board rather than sentiment, flows, or scans.

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 usage context is implied: an agent should call this when it needs the top 24h gainers or losers across major-cap crypto. However, there is no explicit guidance about when to prefer this over alternatives such as scan_market or get_market_sentiment, and no exclusions are stated.

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.