Agent Einstein — Crypto & Market Intelligence

Quantum Risk Assessment

assess_quantum_risk

Read-onlyIdempotent

Assess exposure to cryptographically-relevant quantum computing: organizational PQC readiness, a migration plan, or the quantum risk of a wallet’s address types. [Paid: $0.50–$0.75 per call from your Einstein credit balance. Free alternatives exist for several of these — see list_einstein_capabilities.]

Input Schema

Name	Required	Description	Default
`kind`	No	readiness · migration (needs `walletAddress`) · portfolio (needs `walletAddress`).	readiness
`walletAddress`	No	Wallet to assess, for `portfolio`.

Output 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 changedOct 19, 2026

changedInput schema / properties / kind / description

Previous value: -"readiness · migration · portfolio (needs `walletAddress`)."New value: +"readiness · migration (needs `walletAddress`) · portfolio (needs `walletAddress`)."

Changed2 schema fields changedOct 15, 2026

changedInput schema / properties / kind / description

Previous value: -"readiness · migration · portfolio · crqc_benchmark."New value: +"readiness · migration · portfolio (needs `walletAddress`)."

changedInput schema / properties / kind / enum

Previous value: -[
-  "readiness",
-  "migration",
-  "portfolio",
-  "crqc_benchmark"
-]New value: +[
+  "readiness",
+  "migration",
+  "portfolio"
+]

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.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds the meaningful non-annotation trait: a per-call charge of $0.50–$0.75 drawn from an Einstein credit balance, which the agent must weigh before invoking.

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, front-loaded with capability and closed with the cost/routing caveat. No filler, and the pricing note is set off in brackets so it does not obscure the primary purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A read-only assessment tool with a full output schema, so return values need no explanation. Purpose, mode selection, cost, and cost-free alternatives are all present; nothing an agent needs to call it correctly is missing.

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% and the enum values are fully documented in the schema. The description restates the three modes and the wallet dependency for portfolio/migration, but adds no format, syntax, or constraint detail beyond what the schema already carries.

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?

States a specific verb ('assess') and a narrowly defined resource ('exposure to cryptographically-relevant quantum computing'), then enumerates the three concrete outputs (PQC readiness, migration plan, wallet address-type risk). An agent can distinguish this from every sibling, including the superficially similar generate_quantum_key.

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?

Explicitly flags that this is a paid tool and that free alternatives exist for several modes, routing the agent to list_einstein_capabilities. That is genuine selection guidance, though it stops short of spelling out which specific modes have free substitutes or when cost is justified.

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.