HEY Research Lab

Find a Robinhood Chain project

find_projects

Read-only

Which Robinhood Chain project is this name, $TICKER or 0x contract? Identity only (name, ticker, contract, slug), at most eight rows; give the slug to research_answer. A full 0x address answers whether anyone is building that contract: activity status, ship records in 30 days, the last ship with its source, whether the project names it.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes	Name, $TICKER, slug or 0x contract; q also works.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`api`	Yes
`data`	No
`schema`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026

changedInput schema / properties / query / description

Previous value: -"Name, $TICKER, slug or 0x contract."New value: +"Name, $TICKER, slug or 0x contract; q also works."

Changed1 schema field changedOct 12, 2026

changedInput schema / properties / query / description

Previous value: -"Name, ticker, slug or 0x contract."New value: +"Name, $TICKER, slug or 0x contract."

Changed20 schema fields changedOct 5, 2026

removedInput schema / properties / age

Removed value: -{
-  "description": "Since the first pool opened.",
-  "enum": [
-    "day",
-    "week",
-    "month",
-    "older"
-  ],
-  "type": "string"
-}

removedInput schema / properties / deployed

Removed value: -{
-  "description": "Since the contract was deployed.",
-  "enum": [
-    "day",
-    "week",
-    "month",
-    "older"
-  ],
-  "type": "string"
-}

removedInput schema / properties / has

Removed value: -{
-  "description": "Facts every row must carry.",
-  "items": {
-    "enum": [
-      "token",
-      "x",
-      "marketCap",
-      "launchpad",
-      "liveMarket",
-      "verifiedToken",
-      "trading",
-      "github"
-    ],
-    "type": "string"
-  },
-  "type": "array"
-}

removedInput schema / properties / kind

Removed value: -{
-  "enum": [
-    "UTILITY",
-    "MEME",
-    "HYBRID",
-    "INFRASTRUCTURE",
-    "RWA",
-    "APPLICATION",
-    "OTHER"
-  ],
-  "type": "string"
-}

removedInput schema / properties / launchpad

Removed value: -{
-  "description": "e.g. \"pons\", \"virtuals\".",
-  "maxLength": 40,
-  "type": "string"
-}

removedInput schema / properties / limit

Removed value: -{
-  "description": "Default 24.",
-  "maximum": 48,
-  "minimum": 1,
-  "type": "integer"
-}

removedInput schema / properties / maxMarketCap

Removed value: -{
-  "description": "USD, on the card's valuation reading.",
-  "exclusiveMinimum": 0,
-  "type": "number"
-}

removedInput schema / properties / minLiquidity

Removed value: -{
-  "description": "USD; unknown is excluded, never zero.",
-  "exclusiveMinimum": 0,
-  "type": "number"
-}

removedInput schema / properties / minMarketCap

Removed value: -{
-  "exclusiveMinimum": 0,
-  "type": "number"
-}

removedInput schema / properties / minVolume

Removed value: -{
-  "description": "24h volume, USD.",
-  "exclusiveMinimum": 0,
-  "type": "number"
-}

removedInput schema / properties / narrative

Removed value: -{
-  "description": "Narrative slug, e.g. \"ai-agents\".",
-  "maxLength": 80,
-  "type": "string"
-}

removedInput schema / properties / offset

Removed value: -{
-  "description": "The offset a previous answer gave.",
-  "minimum": 0,
-  "type": "integer"
-}

changedInput schema / properties / query / description

Previous value: -"Name, ticker or contract (or its start)."New value: +"Name, ticker, slug or 0x contract."

changedInput schema / properties / query / maxLength
```
Previous value: -120New value: +64
```

removedInput schema / properties / radar

Removed value: -{
-  "description": "With surface=builder-radar: a Radar view.",
-  "enum": [
-    "all",
-    "pons",
-    "virtuals",
-    "other-launch",
-    "no-token",
-    "new",
-    "established",
-    "most-improved",
-    "development",
-    "onchain",
-    "resumed"
-  ],
-  "type": "string"
-}

removedInput schema / properties / sort

Removed value: -{
-  "description": "Default activity; shipped = newest ship first; shipped7d / shipped30d = most meaningful ships in the last 7 / 30 days.",
-  "enum": [
-    "activity",
-    "shipped",
-    "shipped7d",
-    "shipped30d",
-    "marketCap",
-    "newest",
-    "liquidity",
-    "volume24h"
-  ],
-  "type": "string"
-}

removedInput schema / properties / stage

Removed value: -{
-  "description": "Token launch stage.",
-  "enum": [
-    "curve",
-    "graduated",
-    "dex"
-  ],
-  "type": "string"
-}

removedInput schema / properties / status

Removed value: -{
-  "description": "Activity status.",
-  "enum": [
-    "SHIPPING",
-    "ACTIVE",
-    "QUIET",
-    "DORMANT",
-    "RESUMED",
-    "UNKNOWN"
-  ],
-  "type": "string"
-}

removedInput schema / properties / surface

Removed value: -{
-  "enum": [
-    "building-with-token",
-    "still-building",
-    "under-the-radar",
-    "shipping-now",
-    "most-active",
-    "new-builders",
-    "back-from-dormancy",
-    "utility",
-    "memes",
-    "shipping-in-silence",
-    "accelerating",
-    "builder-radar"
-  ],
-  "type": "string"
-}

addedInput schema / required
```
Added value: +[
+  "query"
+]
```

Changed2 schema fields changedOct 2, 2026

changedInput schema / properties / sort / description

Previous value: -"Default activity; shipped = newest ship first."New value: +"Default activity; shipped = newest ship first; shipped7d / shipped30d = most meaningful ships in the last 7 / 30 days."

changedInput schema / properties / sort / enum

Previous value: -[
-  "activity",
-  "shipped",
-  "marketCap",
-  "newest",
-  "liquidity",
-  "volume24h"
-]New value: +[
+  "activity",
+  "shipped",
+  "shipped7d",
+  "shipped30d",
+  "marketCap",
+  "newest",
+  "liquidity",
+  "volume24h"
+]

Changed2 schema fields changedSep 30, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "api": {
+      "type": "string"
+    },
+    "data": {},
+    "schema": {
+      "const": "hey.mcp-api-answer",
+      "type": "string"
+    }
+  },
+  "required": [
+    "schema",
+    "api"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 30, 2026

changedInput schema / properties / sort / description

Previous value: -"Default activity (card completeness, then activity); shipped = most recently shipped first."New value: +"Default activity; shipped = newest ship first."

First observedSep 28, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds real behavioral detail beyond that: results are capped at eight rows, output is identity-only, and a full 0x address changes the response to activity status, 30-day ship records, last ship with source, and whether the project names the contract. It does not describe no-match or ambiguity behavior.

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?

Two dense sentences, front-loaded with the identity question and then the scope/cap and the 0x-mode behavior. No filler, but the phrasing is compact to the point of being terse ('give the slug to research_answer'), which costs a little readability.

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?

An output schema exists, so return values need no explanation, yet the description usefully summarizes both response modes and the row cap. Gaps remain around fuzzy matching, result ordering, and empty-result handling, but for a single-parameter lookup tool it is largely complete.

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?

With one parameter at 100% schema coverage, the baseline is 3; the description exceeds it by explaining that a full 0x address produces a materially different answer shape than a name/ticker query. It adds semantic meaning the schema does not convey, though it never defines what counts as a 'full' address.

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 frames the tool as resolving a name/$TICKER/0x contract to a Robinhood Chain project identity, listing the exact return fields (name, ticker, contract, slug). This is specific enough that an agent can tell it apart from get_project_timeline or research_answer, though it opens with a question rather than a verb, which makes the core action slightly less immediate.

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 gives a clear downstream routing instruction ('give the slug to research_answer') and describes a distinct usage mode for full 0x addresses. It stops short of stating when NOT to use it (e.g., for contract data, use get_contract), so it is strong context without explicit exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All HEY Research Lab 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.

Find a Robinhood Chain project

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources