Agent Einstein — Crypto & Market Intelligence

Tokenized-Equity Market Intelligence

analyze_tokenized_stocks

Read-onlyIdempotent

The market where memecoins are priced in SHARES, on Base and Robinhood Chain. Float-corner risk (whose on-chain stock float is locked in one pool while the issuer cannot mint), stock-paired launches with their tax and dividend structure on Base AND on Robinhood Chain (~$68M/day of stock-quoted curve volume there — the larger half of this market), who bought a token earliest and who FUNDED those wallets, and which wallets keep entering early and actually realize money. [Paid: $0.25 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
`board`	No	portfolio = deterministic non-executing Coinbase B20 portfolio draft on Base (use `intent`) · float-corner = float concentration + mint window · wrapper-trust = can the wrapper be trusted as COLLATERAL (on-chain rate path, vault-inflation exposure, an unscheduled rate move, pause/permissioning) · stock-pairs = BaseStonk launches priced in an equity (Base) · pons-stock-pairs = Pons launches priced in an equity, and which equity the venue is collectively long (Robinhood Chain 4663) · early-buyers = entry-ranked buyers of one token plus a one-hop funding trace (needs `token`) · trader-record = which wallets are actually good · event-risk = scheduled corporate actions and the implied gap at the open.	float-corner
`token`	No	Token contract address. Required when board=early-buyers.
`intent`	No	Natural-language portfolio objective. Used when board=portfolio; no transactions are executed.

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.

Changed3 schema fields changedSep 15, 2026

changedInput schema / properties / board / description

Previous value: -"float-corner = float concentration + mint window · wrapper-trust = can the wrapper be trusted as COLLATERAL (on-chain rate path, vault-inflation exposure, an unscheduled rate move, pause/permissioning) · stock-pairs = BaseStonk launches priced in an equity (Base) · pons-stock-pairs = Pons launches priced in an equity, and which equity the venue is collectively long (Robinhood Chain 4663) · early-buyers = entry-ranked buyers of one token plus a one-hop funding trace (needs `token`) · trader-record = which wallets are actually good · event-risk = scheduled corporate actions and the implied gap at the open."New value: +"portfolio = deterministic non-executing Coinbase B20 portfolio draft on Base (use `intent`) · float-corner = float concentration + mint window · wrapper-trust = can the wrapper be trusted as COLLATERAL (on-chain rate path, vault-inflation exposure, an unscheduled rate move, pause/permissioning) · stock-pairs = BaseStonk launches priced in an equity (Base) · pons-stock-pairs = Pons launches priced in an equity, and which equity the venue is collectively long (Robinhood Chain 4663) · early-buyers = entry-ranked buyers of one token plus a one-hop funding trace (needs `token`) · trader-record = which wallets are actually good · event-risk = scheduled corporate actions and the implied gap at the open."

changedInput schema / properties / board / enum

Previous value: -[
-  "float-corner",
-  "wrapper-trust",
-  "stock-pairs",
-  "pons-stock-pairs",
-  "early-buyers",
-  "trader-record",
-  "event-risk"
-]New value: +[
+  "float-corner",
+  "wrapper-trust",
+  "stock-pairs",
+  "pons-stock-pairs",
+  "early-buyers",
+  "trader-record",
+  "event-risk",
+  "portfolio"
+]

addedInput schema / properties / intent

Added value: +{
+  "description": "Natural-language portfolio objective. Used when board=portfolio; no transactions are executed.",
+  "type": "string"
+}

Changed2 schema fields changedSep 7, 2026

changedInput schema / properties / board / description

Previous value: -"float-corner = float concentration + mint window · stock-pairs = BaseStonk launches priced in an equity (Base) · pons-stock-pairs = Pons launches priced in an equity, and which equity the venue is collectively long (Robinhood Chain 4663) · early-buyers = entry-ranked buyers of one token plus a one-hop funding trace (needs `token`) · trader-record = which wallets are actually good · event-risk = scheduled corporate actions and the implied gap at the open."New value: +"float-corner = float concentration + mint window · wrapper-trust = can the wrapper be trusted as COLLATERAL (on-chain rate path, vault-inflation exposure, an unscheduled rate move, pause/permissioning) · stock-pairs = BaseStonk launches priced in an equity (Base) · pons-stock-pairs = Pons launches priced in an equity, and which equity the venue is collectively long (Robinhood Chain 4663) · early-buyers = entry-ranked buyers of one token plus a one-hop funding trace (needs `token`) · trader-record = which wallets are actually good · event-risk = scheduled corporate actions and the implied gap at the open."

changedInput schema / properties / board / enum

Previous value: -[
-  "float-corner",
-  "stock-pairs",
-  "pons-stock-pairs",
-  "early-buyers",
-  "trader-record",
-  "event-risk"
-]New value: +[
+  "float-corner",
+  "wrapper-trust",
+  "stock-pairs",
+  "pons-stock-pairs",
+  "early-buyers",
+  "trader-record",
+  "event-risk"
+]

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

Changed2 schema fields changedSep 4, 2026

changedInput schema / properties / board / description

Previous value: -"float-corner = float concentration + mint window · stock-pairs = launches priced in an equity · early-buyers = entry-ranked buyers of one token (needs `token`) · trader-record = which wallets are actually good · event-risk = scheduled corporate actions and the implied gap at the open."New value: +"float-corner = float concentration + mint window · stock-pairs = BaseStonk launches priced in an equity (Base) · pons-stock-pairs = Pons launches priced in an equity, and which equity the venue is collectively long (Robinhood Chain 4663) · early-buyers = entry-ranked buyers of one token plus a one-hop funding trace (needs `token`) · trader-record = which wallets are actually good · event-risk = scheduled corporate actions and the implied gap at the open."

changedInput schema / properties / board / enum

Previous value: -[
-  "float-corner",
-  "stock-pairs",
-  "early-buyers",
-  "trader-record",
-  "event-risk"
-]New value: +[
+  "float-corner",
+  "stock-pairs",
+  "pons-stock-pairs",
+  "early-buyers",
+  "trader-record",
+  "event-risk"
+]

AddedSep 3, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds valuable behavioral context beyond annotations by disclosing the per-call cost ($0.25 from Einstein credit balance) and flagging free alternatives—traits an agent should know 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.

Conciseness4/5

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

The description packs substantial information in two main sentences plus a bracket note, with front-loaded context about the market and a sequence of concrete use cases. It is not excessively long and the paid/free note is clearly delimited. Slight wordiness in the second sentence prevents a 5.

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 a strong annotation stack and 100% schema coverage, the definition only needs to supply operational and pricing context. It does that, plus the board descriptions and the pointer to free paths. The only secondary missing piece is the nuance of 'openWorldHint' and exact response structure, but an output schema exists, keeping the description adequate.

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%, with detailed board meanings already in the input schema. The tool description restates some board concepts in natural language (e.g., 'float-corner risk', 'stock-paired launches'), but it does not define token or new dimensions, so the schema continues to do the heavy lifting. Baseline 3 is appropriate.

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 clearly identifies the tool's focus: market intelligence for 'memecoins priced in SHARES' on Base and Robinhood Chain, and names the major analysis categories (float-corner risk, stock-paired launches, early-buyer traces). It distinguishes the tool from broader siblings by its niche, though it does not explicitly name alternatives.

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 description implies when to use the tool through its market definition and notes that 'free alternatives exist for several of these — see list_einstein_capabilities', which points to alternative pathways. However, it stops short of explicit when/when-not guidance relative to sibling tools like analyze_token_security or analyze_wallet.

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.

Tokenized-Equity Market Intelligence

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources