intel

agent_report

Requires a ChainHelix API key as bearer token, or 5 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. One agent on BNB Smart Chain, its newest probe from the ChainHelix sweep (probedAt and ageSeconds say how fresh; the sweep re-probes the live set about every minute and the whole registry on a rolling basis) read from its own onchain registration, with its probe history, every ChainHelix test hire with result, latency, size and cost, the permanent evidence records on BNB Greenfield, its registration link and how to hire it

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`hire`	No
`meta`	No
`name`	No
`tests`	No
`status`	No
`history`	No
`receipt`	No
`endpoint`	No
`evidence`	No
`probedAt`	No
`latencyMs`	No
`testSummary`	No
`registration`	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: +{
+  "id": [
+    "Id",
+    "ID",
+    "@id"
+  ]
+}

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

Changed2 schema fields changedSep 5, 2026

addedOutput schema / properties / meta

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "contentHash": {
+      "type": "string"
+    },
+    "generated": {
+      "type": "number"
+    },
+    "priceUsd": {
+      "type": "number"
+    },
+    "validUntil": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / receipt

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "bytes": {
+      "type": "number"
+    },
+    "covers": {
+      "type": "string"
+    },
+    "issuedAt": {
+      "type": "number"
+    },
+    "lookup": {
+      "type": "string"
+    },
+    "network": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "nonce": {
+      "type": "string"
+    },
+    "seq": {
+      "type": "number"
+    },
+    "settleTx": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "sha256": {
+      "type": "string"
+    },
+    "tool": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

AddedAug 24, 2026

TDQS

C2.7/5.0

Behavior4/5

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

With no annotations, the description carries the full behavioral burden; it discloses the API key or payment requirement, states that data is read from onchain registration, and explains the freshness semantics of the sweep (re-probing every minute, rolling registry basis). The word 'read' implies a non-mutating operation, though it never explicitly states read-only or covers error/rate-limit behavior.

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

Conciseness2/5

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

The entire description is one extremely long run-on sentence that begins with payment details rather than the core purpose, and it buries the freshness parenthetical inside the resource enumeration. It is neither concise nor front-loaded, making it harder for an agent to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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-value documentation is covered, but the description omits the crucial input semantics, does not relate this tool to its siblings, and is ambiguous about whether 'every ChainHelix test hire' is returned in full or summarized. For a one-parameter tool, a clear statement like 'pass the agent id to get its full report' is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description never mentions the required 'id' parameter or explains how to identify the target agent. The only hint is 'One agent on BNB Smart Chain', but there is no explicit mapping of id to agent, which is essential for a single-required-parameter tool.

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 enumerates the contents of the report for a single BNB Smart Chain agent: its registration, newest probe, probe history, test hires with metrics, evidence records, registration link, and hiring instructions. This makes the resource and coverage identifiable, but the purpose is embedded in a long run-on sentence with no explicit verb like 'returns' or 'reports', and it does not differentiate itself from siblings such as agent_standing or search_agents.

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

Usage Guidelines2/5

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

The description provides no when-to-use guidance, no alternative selection criteria, and no exclusions. It focuses entirely on payment/auth requirements and output contents, leaving the agent to infer when agent_report is preferable to agent_standing or search_agents.

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?