Skip to main content
Glama

intel

by io.chainhelix
OverviewDiscussionsAdmin

hire_plan_gridtrader

Plan a hire of the ChainHelix gridtrader agent (ERC-8004 #269224, Grid trading ladder). Given a mark price and a budget, returns a symmetric buy/sell grid: buy levels below the price, sell levels above, equal USD size per level, and when strong price walls are supplied each level is annotated with its nearest wall and flagged if it sits on one. Deterministic arithmetic, no custody, no execution. Not a bounded-loss or profit-target strategy: fees, slippage, gas and PnL are not computed. 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/gridtrader/.well-known/agent-card.json. Example: {"price":691.65,"budgetUsd":1000,"levels":5,"spanPct":2,"walls":{"677.8":3,"705.5":2}}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lowerNogrid lower bound in price; with upper, an alternative to spanPct
priceNocurrent mark price (also accepted as: mid, midPrice, mark, markPrice, currentPrice, spot)
termsNooptional ERC-8183 terms {deliverables, quality_standards}; the agent quotes its fixed price either way
upperNogrid upper bound in price; with lower, an alternative to spanPct
wallsNoknown support/resistance walls keyed by price, touches is an integer 1 to 10000; levels on a wall are flagged
levelsNogrid lines per side, default 5 (also accepted as: gridLevels, nLevels)
spanPctNohalf-width of the grid in percent, below 100, default 5; or send lower and upper (absolute bounds) and the half-width is derived from the wider side (also accepted as: rangePct, widthPct)
budgetUsdNototal capital to ladder (also accepted as: capitalUsd, budget, capital, notionalUsd, sizeUsd)
wallBandPctNodistance in percent that counts as on a wall, default 0.7

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: +{
+  "budgetUsd": [
+    "budget_usd",
+    "capitalUsd",
+    "budget",
+    "capital",
+    "notionalUsd",
+    "sizeUsd"
+  ],
+  "levels": [
+    "gridLevels",
+    "nLevels"
+  ],
+  "price": [
+    "px",
+    "Price",
+    "_price",
+    "mid",
+    "midPrice",
+    "mark",
+    "markPrice",
+    "currentPrice",
+    "spot"
+  ],
+  "spanPct": [
+    "rangePct",
+    "widthPct"
+  ]
+}
    • 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: +{
+  "budgetUsd": "agent.budgetUsd",
+  "levels": "market.levels",
+  "lower": "market.lower",
+  "price": "market.priceApi",
+  "spanPct": "market.spanPct",
+  "terms": "data.terms",
+  "upper": "market.upper",
+  "wallBandPct": "market.wallBandPct",
+  "walls": "market.walls"
+}
  5. Added

TDQS

A4.5/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 burden and does so excellently: it discloses deterministic arithmetic, no custody, no execution, no fee/slippage/gas/PnL computation, the quote+calldata return flow, and the on-chain escrow funding step. This gives an agent a realistic model of side effects and limits.

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?

The description is longer than average, but every sentence earns its place: purpose, behavior, exclusions, return contract, cost, canonical schema link, and a concrete example. It is front-loaded with the core purpose and avoids filler.

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?

Given the transaction-related workflow and no annotations, the description is remarkably complete: it covers inputs, deterministic behavior, non-goals, output artifacts, funding/escrow, cost model, external canonical reference, and an example. An agent has enough to invoke it correctly and anticipate the follow-up steps.

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 schema already documents every parameter and alias; the baseline is therefore 3. The description adds useful behavioral context for walls and the mark-price/budget relationship, but does not need to explain each parameter further.

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 uses a specific verb ('Plan a hire'), names the exact agent (ChainHelix gridtrader, ERC-8004 #269224), and explains the concrete outcome: a symmetric buy/sell grid with wall annotations. This distinguishes it clearly from sibling hire_plan_* tools that target different agents or strategies.

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 states when to use the tool ('Given a mark price and a budget'), what it will not do ('Not a bounded-loss or profit-target strategy'), and clarifies the free vs. paid job boundary. It does not explicitly name alternative hire_plan_* sibling tools, so the guidance stops short of a full when-not/alternative matrix.

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