Skip to main content
Glama

ChainHelix for Machines

by io.chainhelix.mcp
OverviewDiscussionsAdmin

search_agents

Agents in the ERC-8004 registry on BNB Smart Chain matched by name and description, joined with ChainHelix live status: alive or hireable with probe age for verified agents, unverified for the rest with the free check link. limit default 20, max 50. Price: 2 cents per call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
queryYes
resultsYes
registryTotalNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"670f7504e3de5031beccee25a2d24e4515f68b893295f6d5b0d3a0665498b2c9"New value: +"25cc80db6d8e9eac73d47a50f7ad6333a21f1972d008a8fed0159de8bfb4b519"
  2. Changed2 schema fields changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"New value: +"670f7504e3de5031beccee25a2d24e4515f68b893295f6d5b0d3a0665498b2c9"
    • changedInput schema / x-lexicon / version
      Previous value: -"0.1.0"New value: +"0.2.0"
  3. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedOutput schema / properties / meta
      Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "contentHash": {
-      "type": "string"
-    },
-    "generated": {
-      "type": "number"
-    },
-    "priceUsd": {
-      "type": "number"
-    },
-    "validUntil": {
-      "type": "number"
-    }
-  },
-  "type": "object"
-}
    • removedOutput schema / properties / receipt
      Removed 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"
-}
  4. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"New value: +"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"
  5. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"New value: +"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"
  6. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4"New value: +"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"
  7. Changed3 schema fields changed
    • addedInput schema / x-aliases
      Added value: +{
+  "limit": [
+    "Limit",
+    "limits",
+    "$limit",
+    "_limit",
+    "Limits"
+  ],
+  "query": [
+    "Query",
+    "_query"
+  ]
+}
    • 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: +{
+  "limit": "data.limit",
+  "query": "data.query"
+}
  8. Changed2 schema fields changed
    • 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"
+}
  9. Added

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden, and it does disclose real behavioral facts: the live-status join (alive/hireable with probe age, unverified with free check link), the limit default/max, and pricing at 2 cents per call. It does not cover auth requirements, rate limiting beyond the limit cap, or failure behavior, which for a paid search endpoint would be valuable.

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?

Front-loaded with the resource and matching behavior, then constraints and cost in short trailing sentences. Every sentence carries information; the only mild density issue is the packed status-join clause in the first sentence.

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

Completeness3/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 not be explained, and the description covers purpose, cost, and limits. But with no annotations and no usage routing versus siblings, an agent still lacks the selection context needed to choose this tool confidently over verified_agents.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must compensate. It does clarify query semantics ('matched by name and description') and gives limit's default (20) and max (50), which the schema does not. It adds no format or type detail beyond that, so the two parameters are only partially explained.

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?

States a specific verb+resource (agents in the ERC-8004 registry on BNB Smart Chain) and how matching works (by name and description), plus what the result is joined with. An agent can tell what it does. However, it never explicitly distinguishes itself from the close sibling verified_agents, leaving that differentiation to inference.

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?

There is no when-to-use guidance and no named alternative. With siblings like verified_agents, agent_report, and agent_standing in the same space, the description gives no condition for choosing search_agents over them. It only states cost and result shape.

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

All ChainHelix for Machines toolsInspect
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