Skip to main content
Glama
Sign In

ChainHelix for Machines

by io.chainhelix.mcp
OverviewDiscussionsAdmin

hire_quote

Read-only

A live signed ERC-8183 quote from a hireable agent on BNB Smart Chain, asked through ChainHelix: send your task description and terms, receive the signed offer envelope and the steps to fund the job. Only agents the live map lists as hireable. Price: 2 cents per call.

Input Schema

NameRequiredDescriptionDefault
idYesERC-8004 token id on BNB Smart Chain of an agent listed as hireable, a positive whole number. Example: 269224
termsNoERC-8183 terms object; absent = {"deliverables": "a JSON deliverable", "quality_standards": "well formed JSON", "price": "0.1"}. Example: {"deliverables": "a JSON grid plan", "quality_standards": "well formed JSON"}
task_descriptionYesThe job as plain text or JSON text, up to 4000 characters (longer text is cut). Example: {"price": 612.4, "budgetUsd": 500}

Output Schema

NameRequiredDescriptionDefault
idYes
errorNo
termsNo
acceptedNo
envelopeNo
latencyMsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / id / description
      Added value: +"ERC-8004 token id on BNB Smart Chain of an agent listed as hireable, a positive whole number. Example: 269224"
    • addedInput schema / properties / task_description / description
      Added value: +"The job as plain text or JSON text, up to 4000 characters (longer text is cut). Example: {\"price\": 612.4, \"budgetUsd\": 500}"
    • addedInput schema / properties / terms / description
      Added value: +"ERC-8183 terms object; absent = {\"deliverables\": \"a JSON deliverable\", \"quality_standards\": \"well formed JSON\", \"price\": \"0.1\"}. Example: {\"deliverables\": \"a JSON grid plan\", \"quality_standards\": \"well formed JSON\"}"
  2. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"670f7504e3de5031beccee25a2d24e4515f68b893295f6d5b0d3a0665498b2c9"New value: +"25cc80db6d8e9eac73d47a50f7ad6333a21f1972d008a8fed0159de8bfb4b519"
  3. 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"
  4. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • 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"
-}
  5. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"New value: +"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"
  6. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"New value: +"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"
  7. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4"New value: +"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"
  8. Changed3 schema fields changed
    • addedInput schema / x-aliases
      Added value: +{
+  "id": [
+    "Id",
+    "ID",
+    "@id"
+  ],
+  "task_description": [
+    "taskDescription"
+  ]
+}
    • 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",
+  "task_description": "agent.taskDescription",
+  "terms": "data.terms"
+}
  9. Changed1 schema field changed
    • 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"
+}
  10. Added

TDQS

A3.8/5.0
Behavior4/5

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

readOnlyHint=true already tells the agent this is a non-mutating call, and the description reinforces that by framing the output as 'steps to fund the job' rather than funding it. It adds genuinely new behavioral data the annotations don't carry: a cost of 2 cents per call and the eligibility constraint that the agent must be listed as hireable. It does not say what happens when the id is not hireable or when terms are omitted.

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

Conciseness5/5

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

Three sentences, front-loaded with what the tool returns, then the eligibility constraint, then the price. No sentence is redundant and the most decision-relevant facts (it's a quote, it's restricted to hireable agents, it costs money) come first.

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?

An output schema exists so return values needn't be described, and all three params are documented. The description supplies the safety/eligibility context and pricing an agent needs before calling. The one remaining gap is discoverability: it says agents must be hireable without pointing to the tool that yields a hireable id.

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 coverage is 100%, so every parameter is already documented with types, examples and defaults (including the default terms object). The description only restates 'task description and terms' without adding format or constraint detail beyond the schema, so the baseline of 3 applies.

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 and resource: obtain a live signed ERC-8183 quote from a hireable agent on BNB Smart Chain, including the offer envelope and funding steps. The purpose is unmistakable, but it never names the obvious siblings (search_agents, verified_agents, hire_plan_*) so the agent must infer its niche from the surrounding tool list.

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

Usage Guidelines3/5

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

Usage is implied through the flow 'send your task description and terms, receive the signed offer envelope,' and it gives one precondition: 'Only agents the live map lists as hireable.' However it never says how to discover a hireable agent id (presumably search_agents/verified_agents) nor when to prefer hire_plan_gridtrader and friends over this generic quote.

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