Skip to main content
Glama

ChainHelix for Machines

by io.chainhelix.mcp
OverviewDiscussionsAdmin

lexicon_resolve

One argument name resolved against the ChainHelix Agentic Lexicon: the entry (id, meaning, representation, unit, example) or, when the name is unknown or ambiguous, the candidates to choose from. Optional namespace (common, agent, identity, payment, wallet, onchain, defi, market, data) and venue (an exchange name, e.g. binance: a venue field name resolves through ccxt's mapping). Price: 5 cents per call. A ChainHelix API key does not cover this tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesthe argument name to resolve, e.g. origQty, stop_price, budgetUsd
venueNoexchange name, lower case, e.g. binance
namespaceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
byNo
idNo
okYes
entryNo
reasonNo
chargedNo
spellingNo
candidatesNo
lexiconVersionNo

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. Changed3 schema fields changed
    • changedInput schema / properties / namespace / enum
      Previous value: -[
-  "common",
-  "agent",
-  "identity",
-  "payment",
-  "wallet",
-  "onchain",
-  "defi",
-  "market",
-  "data"
-]New value: +[
+  "common",
+  "agent",
+  "identity",
+  "payment",
+  "wallet",
+  "onchain",
+  "defi",
+  "market",
+  "data",
+  "deal",
+  "barter"
+]
    • 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. 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"
-}
  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. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it discloses cost (5 cents per call), states that a ChainHelix API key does not cover the tool, and explains the branching return behavior (single entry vs candidates on ambiguity). It omits rate limits and any auth requirements beyond the API-key caveat.

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?

A single dense paragraph that front-loads the core action before scope, cost, and auth caveats. Every sentence earns its place, though the return-field enumeration and pricing note make it a touch heavy for one block.

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?

Given an output schema exists, the return shape is already covered, yet the description restates it usefully. It adds the pricing and auth caveats that structured fields do not carry, leaving only minor gaps around rate limits and failure modes.

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 coverage is 67%, so the description needs to add value, and it does: it explains that venue resolves through ccxt's mapping (e.g. binance) and enumerates namespace options. It slightly undersells the namespace enum by listing 9 of the 11 allowed values (deal and barter are missing).

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: resolving one argument name against the ChainHelix Agentic Lexicon, and spells out what comes back (an entry with id/meaning/representation/unit/example, or candidate names when unknown/ambiguous). It never names a sibling (lexicon_bulk, lexicon_spec, lexicon_bundle) to differentiate itself, so it stops short of a 5.

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 rather than stated: you call it to resolve a single field name, optionally scoped by namespace or venue. There is no explicit when-to-use versus the sibling lexicon tools (bulk lookup, spec, bundle), and no prerequisites or exclusion conditions are given.

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