Skip to main content
Glama
Sign In

Agent Einstein — Crypto & Market Intelligence

by io.emc2ai
OverviewDiscussionsAdmin

Arbitrage Scanner

find_arbitrage
Read-onlyIdempotent

Scan for live arbitrage: DEX price dislocations, flash-loan-fundable routes, cross-chain spreads, or prediction-market mispricings. [Paid: $1.00 per call from your Einstein credit balance. Free alternatives exist for several of these — see list_einstein_capabilities.]

Input Schema

NameRequiredDescriptionDefault
kindNoflashloan · cross_chain · prediction_market.prediction_market
chainNoBlockchain network.base
limitNoMaximum results (1-100).

Output Schema

NameRequiredDescriptionDefault
skillNoWhich Einstein capability answered. These tools route onto one of many skills by an enum argument, so this names the branch that actually ran.
reasonNoWhy there is no analysis, when `available` is false.
analysisNoThe written answer, identical to the result's text block. This is the field to read: the rest of the payload is whichever capability answered, and its shape varies by tool and by argument.
availableNoTrue when the analysis ran. False when it did not — no capability matched the arguments, the caller is out of credit, billing was unavailable, or the skill produced nothing. NOT a statement about the market.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / kind / default
      Previous value: -"dex"New value: +"prediction_market"
    • changedInput schema / properties / kind / description
      Previous value: -"dex · flashloan · cross_chain · prediction_market."New value: +"flashloan · cross_chain · prediction_market."
    • changedInput schema / properties / kind / enum
      Previous value: -[
-  "dex",
-  "flashloan",
-  "cross_chain",
-  "prediction_market"
-]New value: +[
+  "flashloan",
+  "cross_chain",
+  "prediction_market"
+]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "analysis": {
+      "description": "The written answer, identical to the result's text block. This is the field to read: the rest of the payload is whichever capability answered, and its shape varies by tool and by argument.",
+      "type": "string"
+    },
+    "available": {
+      "description": "True when the analysis ran. False when it did not — no capability matched the arguments, the caller is out of credit, billing was unavailable, or the skill produced nothing. NOT a statement about the market.",
+      "type": "boolean"
+    },
+    "reason": {
+      "description": "Why there is no analysis, when `available` is false.",
+      "type": "string"
+    },
+    "skill": {
+      "description": "Which Einstein capability answered. These tools route onto one of many skills by an enum argument, so this names the branch that actually ran.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  3. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds the trait annotations cannot express: per-call cost of $1.00 billed against the Einstein credit balance, plus the existence of cheaper alternatives. No rate limits or result-freshness behavior is described, but the paid-operation disclosure is exactly the kind of context annotations cannot carry.

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?

Two sentences, no waste. The capability list is front-loaded and the cost/routing caveat follows immediately after, in the position a reader will actually reach before calling.

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-format explanation is not owed. Given a 3-param, zero-required, paid, read-only tool, the description covers what it does, what it costs, and where to find cheaper options. The one gap is the unmapped 'DEX price dislocations' mode that no `kind` value can request.

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 coverage is 100%, so names, enums, defaults, and ranges are already documented, giving a baseline of 3. The description implicitly glosses the three `kind` values (flash-loan routes, cross-chain spreads, prediction-market mispricings), but its mention of 'DEX price dislocations' corresponds to no enum value, which is a mild ambiguity, and `chain`/`limit` get no extra meaning.

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 names a specific verb (scan) and resource (live arbitrage) and enumerates its sub-domains: DEX price dislocations, flash-loan routes, cross-chain spreads, prediction-market mispricings. This is clearly distinguishable from adjacent siblings like find_yield, detect_mev, and scan_market. It stops short of explicitly contrasting itself with those tools, so it is clear but not sibling-differentiating.

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

Usage Guidelines4/5

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

It gives the key cost condition ($1.00 per call from the credit balance) and routes the agent to alternatives: 'Free alternatives exist for several of these — see list_einstein_capabilities.' That is a genuine when-not-to-use signal, though it does not state which specific free sibling maps to which arbitrage kind, leaving the agent to open list_einstein_capabilities.

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