Agent Einstein — Crypto & Market Intelligence

Uniswap v4 Hook Radar

scan_v4_hooks

Read-onlyIdempotent

Census the Uniswap v4 hook layer on Robinhood Chain (4663) and Base: which hook contracts are creating the most pools, what each is permitted to do to a trader or an LP (take an arbitrary cut of a swap, reject a swap, block a liquidity withdrawal), which sit behind an upgradeable proxy, and which hooks no registry has catalogued. Permissions are decoded from the hook address itself, so they describe capability, not intent — most delta-taking hooks are ordinary launchpads. Robinhood Chain is one of the largest Uniswap v4 venues by volume (the share moves week to week) and a large share of its hooked liquidity is uncatalogued. [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
`chainId`	No	Restrict to one chain. 4663 = Robinhood Chain, 8453 = Base. Omit for both.

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

AddedSep 3, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations confirm it's a read-only, idempotent, open-world operation. The description adds valuable context: permissions are decoded from the hook address (capability, not intent), most delta-taking hooks are ordinary launchpads, and a large share of liquidity is uncatalogued. It also mentions the paid cost. It doesn't disclose rate limits or exact output format, but output schema exists.

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 is front-loaded with the core purpose and scope, then adds crucial caveats (capability vs. intent) and pricing. It is somewhat lengthy but every sentence earns its place by adding interpretative context. No unnecessary repetition.

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?

Given the complexity of the tool (on-chain census with permission decoding and registry gaps), the description provides sufficient context about what is analyzed, the chains involved, the nature of the data, and the cost. It complements the existing output schema and annotations without redundancy.

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%, so the single parameter 'chainId' is fully documented in the schema, including enum meanings and omission behavior. The description doesn't add parameter-level semantics beyond what the schema provides, so 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 uses a specific verb ('Census') and resource ('the Uniswap v4 hook layer') with clear scope (Robinhood Chain 4663 and Base). It differentiates from siblings like scan_launchpads and get_launchpad_radar by focusing on hook contracts, permissions, and registry coverage rather than general launchpads.

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 notes the paid nature and points to 'list_einstein_capabilities' for free alternatives, providing some cost-based guidance. However, it does not explicitly state when to use this tool versus other on-chain analysis tools like scan_launchpads or inspect_onchain, leaving some ambiguity.

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.