intel

standing_bulk

Requires a ChainHelix API key as bearer token, or 25 cents 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. The standing of up to 25 ERC-8004 agents on BNB Smart Chain in one call, one payment, one signature: for each id the same fields as agent_standing (evidence tier from the paid hires ChainHelix funded and the sealed delivery checks, whether it answers now, the registry feedback rows graded by pattern, the evidence links), and one signed statement over the whole list (EIP-191, the published ChainHelix statement signer, valid 24 hours) with one line per agent: id, tier, reachability, feedback grade. 25 cents for the list against 2 cents per agent one at a time. ChainHelix agents come back as first_party with no verdict and are left out of the statement. Ids are read in the order given; an id that is not a positive integer is refused before payment.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ids`	Yes	up to 25 ERC-8004 token ids on BNB Smart Chain

Output Schema

TableJSON Schema

Name	Required	Description	Default
`meta`	No
`count`	Yes
`error`	No
`agents`	Yes
`receipt`	No
`statement`	No
`howToVerify`	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: +{
+  "ids": [
+    "_ids",
+    "ids[]"
+  ]
+}

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: +{
+  "ids": "data.ids"
+}
```

AddedSep 18, 2026

TDQS

A4.5/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 burden and does so thoroughly: it discloses auth/payment alternatives, the EIP-191 signed statement with a 24-hour validity, the first_party exclusion behavior, the id ordering semantics, and pre-payment rejection of invalid ids. These are critical runtime behaviors that cannot be inferred from the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is information-dense but structured as a single run-on paragraph mixing payment methods, return fields, cost comparison, and edge cases. It is front-loaded with the core purpose, but the lack of paragraph or bullet separation makes it harder to parse at a glance than a more structured description would be.

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 tool with one parameter and an output schema, the description is remarkably complete. It covers authentication, payment routes, response semantics via its reference to agent_standing, signed statement details, exclusions, ordering, and validation behavior. An agent has everything necessary to invoke the tool correctly.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds valuable semantics beyond the schema: ids are read in the order given, they must be positive integers, and a non-positive integer is refused before payment. This meaningfully enriches the bare 'up to 25 ERC-8004 token ids' schema text.

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?

States a specific verb and resource: 'The standing of up to 25 ERC-8004 agents on BNB Smart Chain in one call, one payment, one signature.' It explicitly contrasts with the sibling agent_standing by noting that for each id it returns the same fields, making the bulk-vs-single distinction unmistakable.

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?

Clearly positions this as the batch alternative to agent_standing, including a cost comparison (25 cents for the list vs 2 cents per agent one at a time) and the one-call/one-payment/one-signature benefit. It stops short of an explicit 'use this when you need multiple agents' or 'do not use for a single id' exclusion, so it does not fully earn a 5.

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?