Skip to main content
Glama

intel

by io.chainhelix
OverviewDiscussionsAdmin

hire_plan_healthmon

Plan a hire of the ChainHelix healthmon agent (ERC-8004 #269228, Position health report). Lending health: given collateral rows with liquidation thresholds, debt and prices, returns the health factor, its status (healthy, warning, critical, liquidatable) and per-asset liquidation prices with drop distances. LP range health: send position {price, lowerPrice, upperPrice} instead of collateral and debt. One question per job. Deterministic arithmetic, no custody, no execution. Send the job parameters; you get back the agent's live wallet-signed quote (the job price, paid into escrow on chain when you fund) and the createJob calldata to sign from YOUR wallet, then fund and tell the agent (steps in the answer). This call is free; the job is not. The parameters here are exactly what the agent accepts; the same schema is on its agent card at https://agents.chainhelix.io/healthmon/.well-known/agent-card.json. Example: {"collateral":{"ETH":{"amount":10,"liqThreshold":0.8}},"debt":{"USDT":10000},"prices":{"ETH":2000,"USDT":1}}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
debtNooutstanding debt per symbol; required unless `position` is sent (also accepted as: debts, borrowed, borrows, loans)
termsNooptional ERC-8183 terms {deliverables, quality_standards}; the agent quotes its fixed price either way
wallsNowith position only: strong levels keyed by price, each range edge is annotated with the nearest one
pricesNoa mark for every collateral and debt symbol (also accepted as: marks, quotes, pricesUsd)
alertHFNowarning level, default 1.5
positionNoPancakeSwap v3 LP range health instead of lending health (do not send with collateral or debt); optional nearEdgePct, feesEarnedUsd, positionValueUsd, ageDays; returns range status, distance to each edge, position inside the band and the fee run-rate (also accepted as: lpPosition, range)
collateralNoliqThreshold in (0, 1]; required unless `position` is sent (also accepted as: collaterals, supplied, deposits)
criticalHFNocritical level, must be below alertHF, default 1.1

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
txNo
nextNo
planNo
agentYes
errorNo
exampleNo
missingNo
envelopeNo
expectedNo
erc8004IdNo

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. Changed3 schema fields changed
    • addedInput schema / x-aliases
      Added value: +{
+  "collateral": [
+    "collaterals",
+    "supplied",
+    "deposits"
+  ],
+  "debt": [
+    "debts",
+    "borrowed",
+    "borrows",
+    "loans"
+  ],
+  "position": [
+    "Position",
+    "_position",
+    "lpPosition",
+    "range"
+  ],
+  "prices": [
+    "marks",
+    "quotes",
+    "pricesUsd"
+  ]
+}
    • 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: +{
+  "alertHF": "defi.alertHF",
+  "collateral": "defi.collateral",
+  "criticalHF": "defi.criticalHF",
+  "debt": "defi.debt",
+  "position": "data.position",
+  "prices": "market.prices",
+  "terms": "data.terms",
+  "walls": "market.walls"
+}
  5. Changed2 schema fields changed
    • addedInput schema / anyOf
      Added value: +[
+  {
+    "required": [
+      "collateral",
+      "debt",
+      "prices"
+    ]
+  },
+  {
+    "required": [
+      "position"
+    ]
+  }
+]
    • changedInput schema / description
      Previous value: -"Required: collateral, debt, prices. Each property description lists the other names accepted for it. Example: {\"collateral\":{\"ETH\":{\"amount\":10,\"liqThreshold\":0.8}},\"debt\":{\"USDT\":10000},\"prices\":{\"ETH\":2000,\"USDT\":1}}"New value: +"Required: . Each property description lists the other names accepted for it. Example: {\"collateral\":{\"ETH\":{\"amount\":10,\"liqThreshold\":0.8}},\"debt\":{\"USDT\":10000},\"prices\":{\"ETH\":2000,\"USDT\":1}}"
  6. Added

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so well: it discloses deterministic arithmetic, no custody, no execution, the free-vs-paid nature of the call versus the job, and the expected workflow of receiving a quote and calldata before funding. This goes well beyond what the schema conveys.

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 dense but front-loaded with the core purpose, then logically moves through modes, workflow, and example. Every sentence contributes useful information, though the paragraph is long enough that a little more structure (e.g., separating modes) could improve scannability.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with nested objects, two mutually exclusive modes, and an on-chain workflow, the description covers the necessary context: both modes, the job parameters, the free-call distinction, the wallet-signed quote and calldata steps, and a valid example. The output schema exists, so return-value details are not required in the description.

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%, so the baseline is 3. The description adds a concrete example and clarifies the mutually exclusive position-vs-collateral/debt groups, but does not need to explain each parameter because the schema already documents them thoroughly.

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 opens with a specific verb and resource: 'Plan a hire of the ChainHelix healthmon agent (ERC-8004 #269228, Position health report).' It then distinguishes the two supported modes (lending health and LP range health), making its purpose unmistakable and separating it from sibling hire_plan tools.

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?

The description gives clear when-to-use guidance for both input variants: send collateral/debt/prices for lending health, or send position for LP range health. It also states operational boundaries ('One question per job', 'no custody, no execution'), though it does not explicitly name sibling alternatives such as hire_quote.

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