Skip to main content
Glama

intel

by io.chainhelix
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: -"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"New value: +"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"
  2. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"New value: +"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"
  3. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4"New value: +"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"
  4. 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"
+}
  5. 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"
+  ]
+}
  6. 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"
+}
  7. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations provided, the description must carry the behavioral burden. It discloses that the check is free, returns content hash and validUntil, and explains the requiresArguments behavior. It also clarifies that the paid answer carries its own meta.contentHash, giving full transparency without contradiction.

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 description is longer than average but each sentence adds value: purpose, mechanics, and edge case. It front-loads the core purpose and orders information logically, making it efficient to parse despite its length.

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 the output schema exists and the description explains the primary use case, the optional parameter, and the requiresArguments nuance, the tool is adequately described for an agent to use correctly. No critical missing information for the tool's simple interface.

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?

The input schema already covers the parameter 'name' with 'one data tool to check; omit for all' and 100% coverage. The description only reiterates this ('Optional name for one tool') without adding new meaning, so it does not go beyond the schema baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: providing content hash and validUntil for data tools' default results, enabling users to check freshness before purchasing. It distinguishes itself from data-providing siblings by being a meta-check tool, and the concrete details (hash, validUntil, chains) make it unambiguous.

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 explicitly frames the tool as a 'Free check before you pay' and explains that if the hash matches, no purchase is needed. It also covers the edge case for tools requiring arguments, noting they have no default result and their paid answer carries its own contentHash. While it does not name alternative tools, the purchasing context is clear enough for an agent to know when to invoke it.

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

All intel 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