Agent Einstein — Crypto & Market Intelligence

Yield Opportunity Finder

find_yield

Read-onlyIdempotent

Find yield: DeFi lending and LP opportunities ranked by risk-adjusted return, Pendle fixed-yield and YT/PT trades, a broad vault discovery sweep, or liquidation opportunities. [Paid: $0.10–$0.75 per call from your Einstein credit balance. Free alternatives exist for several of these — see list_einstein_capabilities.]

Input Schema

TableJSON Schema

Name	Required	Description	Default
`kind`	No	defi · pendle · discover · liquidations.	defi
`chain`	No	Blockchain network. `robinhoodchain` covers the Pendle NVDA/PFE markets.	base
`limit`	No	Maximum results (1-100).

Output Schema

TableJSON Schema

Name	Required	Description
`skill`	No	Which Einstein capability answered. These tools route onto one of many skills by an enum argument, so this names the branch that actually ran.
`reason`	No	Why there is no analysis, when `available` is false.
`analysis`	No	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.
`available`	No	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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 11, 2026

changedInput schema / properties / chain / description

Previous value: -"Blockchain network."New value: +"Blockchain network. `robinhoodchain` covers the Pendle NVDA/PFE markets."

changedInput schema / properties / chain / enum

Previous value: -[
-  "base",
-  "ethereum",
-  "bsc",
-  "arbitrum",
-  "polygon",
-  "optimism",
-  "solana"
-]New value: +[
+  "base",
+  "ethereum",
+  "bsc",
+  "arbitrum",
+  "polygon",
+  "optimism",
+  "solana",
+  "robinhoodchain"
+]

Changed1 schema field changedSep 4, 2026

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"
+}

AddedAug 17, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the burden is light, and the description adds genuinely new behavioral context: per-call cost ($0.10–$0.75), that it draws on an Einstein credit balance, and that cheaper/free alternatives exist via list_einstein_capabilities. It does not, however, describe rate limits or result freshness.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the four modes and trailing with the pricing caveat, so the actionable content comes first. The bracket cost note is dense but earns its place; the enumeration is long but not padded.

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?

With an output schema present the description needn't explain return values, and the rich annotations cover the safety profile. Cost, alternatives, and the four modes are all covered, leaving only minor gaps around result freshness and per-kind behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description does more than repeat the schema: it expands each `kind` enum value into a concrete opportunity category, which is meaningful semantic scaffolding for selecting the mode. `chain` and `limit` remain purely schema-documented.

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 uses a specific verb+resource ('Find yield') and enumerates the four distinct opportunity classes (DeFi lending/LP, Pendle fixed-yield YT/PT, vault discovery sweep, liquidations) that map 1:1 to the `kind` enum, letting an agent separate it from siblings like find_arbitrage 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 four modes are described in the order of the `kind` values, which implicitly tells the agent which kind yields which output, and it flags that free alternatives exist for some modes. However, it never explicitly states when to choose one kind over another or when to prefer this tool over competitor siblings, leaving routing largely 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.