Agent Einstein — Crypto & Market Intelligence

Token Security Analysis

analyze_token_security

Read-onlyIdempotent

Live security analysis of a token contract: rug-pull risk, holder concentration, sniper activity, dangerous approvals, or a full smart-contract audit. Choose the analysis with kind. [Paid: $0.35–$2.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	rug_pull = honeypot/rug risk scan · holders = concentration · sniping = launch-sniper activity · approvals = risky token approvals for a wallet · contract_audit = full source audit.	rug_pull
`chain`	No	Blockchain network.	base
`tokenAddress`	Yes	Token contract 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.2/5.0

Behavior4/5

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

The annotations already declare read-only, idempotent, and open-world traits. The description adds cost information ($0.35–$2.00 per call) and notes the existence of free alternatives, which are not covered by the annotations. It does not contradict the annotations.

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 concise, with two sentences that front-load the core purpose and then provide usage and cost context. No unnecessary fluff or redundant phrasing.

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?

Given the output schema exists and the parameters are fully described, the description provides sufficient context: purpose, kind selection, and cost. It does not explain return values, but that is not required since an output schema is present. The cost and alternative note add valuable context.

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 coverage for parameters is 100%: each parameter has a clear description and enum values for `kind` and `chain` are explained. The description only reinforces the `kind` parameter's role and does not add new semantic details beyond the schema, so it stays at the baseline.

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 clearly states it performs live security analysis of a token contract, listing specific risk types (rug-pull, holder concentration, sniper activity, approvals, full audit) and instructs to choose the analysis via the `kind` parameter. This distinguishes it from sibling tools like bitcoin analysis or copy trading, making its purpose unambiguous.

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?

It mentions that free alternatives exist for several kinds and points to list_einstein_capabilities, providing a useful comparison. However, it does not explicitly specify conditions for when to prefer this paid tool over alternatives like check_token_safety or inspect_onchain, so it falls short of fully explicit guidance.

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.