Agent Einstein — Crypto & Market Intelligence

Wallet Analysis

analyze_wallet

Read-onlyIdempotent

Analyze any wallet address: current holdings, realized/unrealized P&L, a trust score, forgotten or dust assets, unclaimed airdrops, or quantum-resistance of its address type. [Paid: $0.25–$1.00 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	portfolio = holdings · pnl = profit and loss x-ray · trust = trust score · forgotten = stranded assets · airdrops = unclaimed airdrops · quantum = post-quantum exposure.	portfolio
`chain`	No	Blockchain network.	base
`walletAddress`	Yes	Wallet address to analyze.

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.

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 establish readOnlyHint, idempotentHint, openWorldHint, and non-destructiveness, so the bar for additional behavioral disclosure is lower. The description adds valuable context beyond annotations: it is a paid call costing $0.25–$1.00 from the credit balance, and free alternatives exist for some analyses. This helps an agent decide whether to invoke the tool.

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?

The description is a single, front-loaded sentence covering the core purpose and analysis modes, followed by a compact paid/alternative note. Every clause carries useful information and there is no filler or repetition 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?

With an output schema, detailed enum descriptions, and safety annotations already present, the description does not need to restate return values or side-effect guarantees. It covers purpose, pricing, and alternative routes well. It would be more complete with explicit guidance on supported chains or overlap with sibling tools, but nothing critical is missing for invoking the tool correctly.

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 description coverage is 100%, so the baseline is 3. The description adds useful semantic gloss over the kind enum: 'current holdings' maps to portfolio, 'realized/unrealized P&L' maps to pnl, 'forgotten or dust assets' maps to forgotten, and 'quantum-resistance of its address type' maps to quantum. It does not add detail for chain or walletAddress, but the schema already documents those.

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 opens with a specific verb and resource — 'Analyze any wallet address' — and enumerates six concrete analysis outputs (holdings, P&L, trust score, forgotten assets, airdrops, quantum-resistance). It is clearly scoped to wallet-level analysis, but it does not explicitly differentiate itself from siblings like assess_quantum_risk or analyze_bitcoin, so it stops short of a 5.

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?

The main usage context is clear: use this when the agent needs any of the listed wallet analyses. The description also points to free alternatives via list_einstein_capabilities, which is a useful routing signal. However, it does not state explicit when-not-to-use conditions or name which alternatives cover which sub-analyses.

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.