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, portfolio-level quantum risk, or how close a CRQC actually is by current benchmarks. [Paid: $0.50–$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	readiness · migration · portfolio · crqc_benchmark.	readiness
`walletAddress`	No	Wallet to assess, for `portfolio`.

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.5/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 the safety profile is covered. The description adds important behavioral context beyond the annotations: the call is paid from Einstein credit balance, pricing ranges from $0.50-$1.00, and the assessment draws on 'current benchmarks.' This helps an agent understand practical implications of invoking 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 one dense, front-loaded sentence followed by a short billing note. Every phrase earns its place: the core purpose is stated first, the four variants are listed compactly, and the cost/alternative guidance is separated in brackets. No wasted words and no structural clutter.

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?

For a tool with two optional parameters, full schema description coverage, an output schema, and read-only/idempotent annotations, this description is complete. It explains what the tool assesses, names all four kinds, notes the cost, and gives an explicit pointer for free alternatives. An agent has everything needed to decide whether and how to call it 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 coverage is 100%, so the baseline is 3, but the description adds useful plain-language meaning to the 'kind' enum: 'organizational PQC readiness' maps to readiness, 'a migration plan' to migration, 'portfolio-level quantum risk' to portfolio, and 'how close a CRQC actually is' to crqc_benchmark. It does not explicitly discuss walletAddress, but the schema already covers that sufficiently.

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 and resource — 'Assess exposure to cryptographically-relevant quantum computing' — and then enumerates the four concrete assessment types: PQC readiness, migration plan, portfolio-level risk, and CRQC benchmark. This maps cleanly to the tool's purpose and distinguishes it from every sibling tool, none of which addresses quantum risk assessment.

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 description clearly signals that this is a paid tool and directs the agent to list_einstein_capabilities for free alternatives, providing meaningful context for when not to use it. It does not give explicit when-to-use/when-not-to-use conditions beyond this, but the cost warning and pointer to alternatives are clear and actionable.

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.