intel

stream_register_all

10 dollars per call paid over Binance b402 in USDT, USDC, USD1 or U on BNB Smart Chain, or over x402 in USDC on the Base network. A ChainHelix API key does not cover this tool. The MEV order flow stream PUSHED to your https URL for all four chains at once (bnb, ethereum, polygon, avalanche): one signed message per chain per completed minute with detected MEV, each carrying the per-pool rows of that minute. 10 dollars buys 7 days of every chain, against 4 dollars per chain one at a time with stream_register. Call again to renew. Manage with webhook_status and webhook_unregister; the contract is in mev_flow_spec

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No
`url`	No
`note`	No
`chain`	No
`error`	No
`chains`	No
`events`	No
`secret`	No
`receipt`	No
`daysAdded`	No
`expiresAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 21, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"New value: +"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"

Changed1 schema field changedSep 19, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"New value: +"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"

Changed1 schema field changedSep 19, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4"New value: +"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"

Changed3 schema fields changedSep 19, 2026

addedInput schema / x-aliases

Added value: +{
+  "url": [
+    "Url",
+    "URL"
+  ]
+}

addedInput schema / x-lexicon

Added value: +{
+  "bundleSha256": "c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4",
+  "name": "ChainHelix Agentic Lexicon",
+  "resolve": "lexicon_resolve",
+  "spec": "lexicon_spec",
+  "version": "0.1.0"
+}

addedInput schema / x-vocab
```
Added value: +{
+  "url": "data.url"
+}
```

AddedSep 16, 2026

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations provided, the description carries the full disclosure burden. It discloses the per-call cost, payment methods, the fact that API keys do not cover this tool, the push cadence (one signed message per chain per completed minute), the payload contents, the 7-day validity, and renewal behavior. This leaves little hidden about side effects or ongoing 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?

The description is dense but every sentence earns its place, covering pricing, payment, delivery behavior, comparison, renewal, and management. However, it front-loads billing and payment details before stating the core function, which somewhat delays orientation for the agent.

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?

For a billing and stream-registration tool with one parameter and an output schema, the description covers scope, payload shape, cost, payment rails, validity, renewal, management siblings, and spec references. Nothing essential is missing for an agent to decide whether and how to call it.

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?

The schema only defines url as a required string, with 0% description coverage. The description compensates by stating the url must be an HTTPS endpoint and is the destination receiving the pushed stream. It does not add format or validation details beyond HTTPS, but for a single simple parameter this is sufficient.

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 identifies the tool's function: it registers a multi-chain MEV order flow stream that is pushed to a supplied HTTPS URL for bnb, ethereum, polygon, and avalanche simultaneously. It also distinguishes itself from the sibling stream_register by emphasizing the "all four chains at once" scope and bundled pricing, so an agent can tell what this tool uniquely does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit cost/scope comparison with stream_register: $10 for 7 days of every chain versus $4 per chain one at a time, which effectively tells the agent when to prefer this tool. It also routes lifecycle management to webhook_status and webhook_unregister and points to mev_flow_spec for the contract, providing clear operational guidance.

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

All intel 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.

Resources

Need Help?