Skip to main content
Glama

ChainHelix for Machines

by io.chainhelix.mcp
OverviewDiscussionsAdmin

freshness

Free check before you pay: for every data tool, the content hash and validUntil of its current default result (all chains). If the hash matches what you already hold, nothing changed and there is nothing to buy. A tool that needs arguments has no default result and is listed with requiresArguments; its paid answer carries its own meta.contentHash. Optional name for one tool

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoone data tool to check; omit for all (also accepted as: tool)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNo
toolsYes
checkedAtYes

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. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  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. Changed4 schema fields changed
    • addedInput schema / properties / name / description
      Added value: +"one data tool to check; omit for all (also accepted as: tool)"
    • addedInput schema / x-aliases
      Added value: +{
+  "name": [
+    "Name",
+    ":name",
+    "_name",
+    "NAME",
+    "tool"
+  ]
+}
    • 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: +{
+  "name": "agent.name"
+}
  8. Changed3 schema fields changed
    • addedOutput schema / properties / tools / items / properties / note
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / tools / items / properties / reason
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / tools / items / properties / requiresArguments
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}
  9. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "checkedAt": {
+      "type": "number"
+    },
+    "note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "tools": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "cached": {
+            "type": [
+              "boolean",
+              "null"
+            ]
+          },
+          "contentHash": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "error": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "generated": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "name": {
+            "type": "string"
+          },
+          "priceUsd": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "validUntil": {
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "checkedAt",
+    "tools"
+  ],
+  "type": "object"
+}
  10. Added

TDQS

A3.9/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 burden and does well: it discloses the tool is free, enumerates all chains, explains the requiresArguments marker for tools without a default result, and points at meta.contentHash in paid answers. It omits auth requirements and rate limits, but for a free read-only check those are minor gaps.

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?

The value proposition is front-loaded in the first clause ('Free check before you pay'), and every following sentence adds a distinct fact — match semantics, the requiresArguments case, the paid-answer hash. It is dense and slightly run-on, but nothing is filler.

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 need no explanation, and the description covers the one real gotcha an agent would hit (argument-requiring tools appearing with requiresArguments). For a one-optional-parameter read tool this is nearly complete; only auth/cost-limit details are absent.

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 100% and the single optional 'name' parameter is fully documented in the schema (including the 'tool' alias). The description's 'Optional name for one tool' only restates that, so the baseline of 3 applies; the requiresArguments discussion adds related behavioral context but not new parameter semantics.

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 states a specific resource and return payload: the content hash and validUntil of each data tool's current default result, framed as a free pre-purchase check. The opaque name 'freshness' is rescued by the prose, and the tool is clearly distinct from siblings like data_changelog or instrument_state, though no sibling is named explicitly.

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?

It gives a clear when-to-use rule — 'free check before you pay' — plus the decision logic ('if the hash matches what you already hold, nothing changed and there is nothing to buy'). It also explains how to interpret entries for tools that need arguments. No alternative tool is named, which keeps it short of a 5.

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