HEY Research Lab

What changed on Robinhood Chain

get_changes

Read-only

What changed on Robinhood Chain today or this week, or for one project or contract? The change ledger without market readings: releases, ships, status moves, contract deploys and upgrades, verification, sources, unlocks — one event per change with its own time and precision, when HEY first knew, and its evidence. Newest first by first arrival; for today pass detectedSince; to sync, pass after=c1.0 and keep each cursor. A retraction means HEY no longer makes that claim. Facts, never causes.

Input Schema

Name	Required	Description
`type`	No	Keep only these event types.
`after`	No	Sync forward from this cursor (c1.0 is the start).
`limit`	No	Default 30.
`since`	No	ISO date: events whose own time is at or after it (events with no source time are left out).
`until`	No	ISO date: events whose own time is before it.
`before`	No	Browse older than this cursor.
`domain`	No	Keep only these domains.
`project`	No	A project slug.
`contract`	No	<chainId>:<address>.
`detectedSince`	No	ISO instant: start a sync at the first event HEY recorded at or after it.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 5, 2026
- addedInput schema / properties / domain / description
```
Added value: +"Keep only these domains."
```
- addedInput schema / properties / type / description
```
Added value: +"Keep only these event types."
```
- addedInput schema / properties / until / description
```
Added value: +"ISO date: events whose own time is before it."
```

Changed1 schema field changedOct 15, 2026

changedInput schema / properties / type / items / enum

Previous value: -[
-  "build.release",
-  "build.code_activity",
-  "build.ship",
-  "build.status_changed",
-  "build.dormant",
-  "build.resumed",
-  "build.accelerating",
-  "build.slowing",
-  "contract.deployed",
-  "contract.followup_deployed",
-  "contract.implementation_changed",
-  "contract.source_verified",
-  "contract.source_unverified",
-  "contract.interface_changed",
-  "contract.usage_changed",
-  "contract.method_first_observed",
-  "contract.method_resumed",
-  "token.launch_stage_changed",
-  "token.verification_changed",
-  "research.published",
-  "research.builder_verified",
-  "research.owner_verified",
-  "research.source_added",
-  "research.source_unavailable",
-  "research.source_restored",
-  "research.source_changed",
-  "research.narrative_assigned",
-  "lock.unlock_due",
-  "lock.observed",
-  "lock.withdrawn"
-]New value: +[
+  "build.release",
+  "build.code_activity",
+  "build.ship",
+  "build.status_changed",
+  "build.dormant",
+  "build.resumed",
+  "build.accelerating",
+  "build.slowing",
+  "contract.deployed",
+  "contract.followup_deployed",
+  "contract.implementation_changed",
+  "contract.source_verified",
+  "contract.source_unverified",
+  "contract.interface_changed",
+  "contract.usage_changed",
+  "contract.method_first_observed",
+  "contract.method_resumed",
+  "contract.v4_pool_initialized",
+  "token.launch_stage_changed",
+  "token.verification_changed",
+  "research.published",
+  "research.builder_verified",
+  "research.owner_verified",
+  "research.source_added",
+  "research.source_unavailable",
+  "research.source_restored",
+  "research.source_changed",
+  "research.narrative_assigned",
+  "lock.unlock_due",
+  "lock.observed",
+  "lock.withdrawn"
+]

Changed2 schema fields changedOct 5, 2026

changedInput schema / properties / domain / items / enum

Previous value: -[
-  "build",
-  "contract",
-  "market",
-  "token",
-  "research",
-  "lock",
-  "market_integrity"
-]New value: +[
+  "build",
+  "contract",
+  "token",
+  "research",
+  "lock"
+]

changedInput schema / properties / type / items / enum

Previous value: -[
-  "build.release",
-  "build.code_activity",
-  "build.ship",
-  "build.status_changed",
-  "build.dormant",
-  "build.resumed",
-  "build.accelerating",
-  "build.slowing",
-  "contract.deployed",
-  "contract.followup_deployed",
-  "contract.implementation_changed",
-  "contract.source_verified",
-  "contract.source_unverified",
-  "contract.interface_changed",
-  "contract.usage_changed",
-  "contract.method_first_observed",
-  "contract.method_resumed",
-  "market.status_changed",
-  "market.liquidity_moved",
-  "market.volume_spike",
-  "market.distribution_changed",
-  "token.launch_stage_changed",
-  "token.verification_changed",
-  "research.published",
-  "research.builder_verified",
-  "research.owner_verified",
-  "research.source_added",
-  "research.source_unavailable",
-  "research.source_restored",
-  "research.source_changed",
-  "research.narrative_assigned",
-  "lock.unlock_due",
-  "lock.observed",
-  "lock.withdrawn",
-  "market_integrity.event"
-]New value: +[
+  "build.release",
+  "build.code_activity",
+  "build.ship",
+  "build.status_changed",
+  "build.dormant",
+  "build.resumed",
+  "build.accelerating",
+  "build.slowing",
+  "contract.deployed",
+  "contract.followup_deployed",
+  "contract.implementation_changed",
+  "contract.source_verified",
+  "contract.source_unverified",
+  "contract.interface_changed",
+  "contract.usage_changed",
+  "contract.method_first_observed",
+  "contract.method_resumed",
+  "token.launch_stage_changed",
+  "token.verification_changed",
+  "research.published",
+  "research.builder_verified",
+  "research.owner_verified",
+  "research.source_added",
+  "research.source_unavailable",
+  "research.source_restored",
+  "research.source_changed",
+  "research.narrative_assigned",
+  "lock.unlock_due",
+  "lock.observed",
+  "lock.withdrawn"
+]

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

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 and openWorldHint, but the description adds real behavior: results are 'newest first by first arrival', 'one event per change with its own time and precision, when HEY first knew', and that a retraction means the claim is withdrawn. It also states the epistemics ('Facts, never causes'). Missing are rate limits or error behavior, but the added semantics go well beyond 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.

Conciseness4/5

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

The scoping question is front-loaded before the ledger definition and cursor instructions, and the phrasing is dense but purposeful. A few fragments ('Facts, never causes.') and the em-dash list are stylistic load rather than wasted space, though they slightly slow comprehension.

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?

For a 10-parameter, zero-required read tool with an output schema, the description covers scope, ordering, cursor/sync protocol, and retraction semantics, which is what an agent needs to call it correctly. It leaves the query-mode selection (since vs detectedSince vs after) partially inferable rather than fully spelled out, keeping it from a 5.

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 100% schema coverage the baseline is 3, but the description earns more by explaining the ordering model ('newest first by first arrival') that governs the after/before cursors and by clarifying the distinction between an event's own time and 'when HEY first knew it' (since vs detectedSince). That resolves the trickiest ambiguity in the parameter set.

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 opens with a concrete question ('What changed on Robinhood Chain today or this week, or for one project or contract?') and defines the resource as a 'change ledger' enumerating releases, ships, status moves, deploys, verification, sources and unlocks. 'Without market readings' carves out scope, but no sibling tool (get_project_timeline, get_evidence, explain_fact) is named for contrast, so the agent must infer the boundary.

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?

Clear invocational guidance is given: 'for today pass detectedSince; to sync, pass after=c1.0 and keep each cursor', which tells the agent exactly which mode to pick. There is no explicit when-not guidance or routing to alternatives like get_project_timeline for the same project view, so it stops short of full alternative coverage.

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.