Skip to main content
Glama
Sign In

ChainHelix for Machines

by io.chainhelix.mcp
OverviewDiscussionsAdmin

hire_plan_yieldopt

Read-only

Plan a hire of the ChainHelix yieldopt agent (ERC-8004 #269226, Yield allocation across pools). Given candidate pools with APY, optional TVL and risk score, and the capital to place, returns the allocation per pool under concentration and TVL-share caps, the blended APY and any capital left unallocated because a cap bound first. 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; an example is in the input schema description.

Input Schema

NameRequiredDescriptionDefault
poolsNocandidate pools keyed by name; riskScore 1 (safest) to 5, default 3 (also accepted as: opportunities, vaults, farms)
termsNooptional ERC-8183 terms {deliverables, quality_standards}; the agent quotes its fixed price either way
tvlCapPctNomax share of a pool's TVL to hold, default 5
capitalUsdNocapital to allocate (also accepted as: budgetUsd, capital, budget, amountUsd)
riskAversionNo0 chases raw APY, 1 applies the full risk discount, default 0.5
maxPerPoolPctNomax share of capital in one pool, at most 100, default 40

Output 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: -"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
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"New value: +"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"
  4. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"New value: +"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"
  5. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4"New value: +"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"
  6. Changed3 schema fields changed
    • addedInput schema / x-aliases
      Added value: +{
+  "capitalUsd": [
+    "budget_usd",
+    "budgetUsd",
+    "capital",
+    "budget",
+    "amountUsd"
+  ],
+  "pools": [
+    "pool",
+    "_pool",
+    "opportunities",
+    "vaults",
+    "farms"
+  ]
+}
    • 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: +{
+  "capitalUsd": "agent.budgetUsd",
+  "maxPerPoolPct": "defi.maxPerPoolPct",
+  "pools": "defi.pool",
+  "riskAversion": "defi.riskAversion",
+  "terms": "data.terms",
+  "tvlCapPct": "defi.tvlCapPct"
+}
  7. Added

TDQS

A4.2/5.0
Behavior5/5

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

Goes far beyond readOnlyHint=true by stating 'Deterministic arithmetic, no custody, no execution' and clarifying the money flow: the call is free but funding pays the job price into on-chain escrow, signed from the caller's own wallet. It also discloses determinism and the existence of follow-up steps, which the annotations cannot convey.

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?

Front-loads the purpose and the distinguishing domain in the first clause, then moves to inputs, outputs, and cost model. It is dense but nearly every sentence carries information; the closing note about parameters matching the agent's accepted schema and the example pointer is mildly redundant with the schema itself.

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?

Covers inputs, output shape (allocation per pool, blended APY, unallocated capital), cost, and the funding handoff, all for a tool that also has an output schema. Remaining ambiguity is mainly verb-level operational detail (how/where to sign and fund), which it defers to 'steps in the answer'.

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 100% with defaults and aliases documented per property, so the baseline is 3. The description adds real semantics by grouping the inputs into candidate pools (APY, optional TVL, risk score) and the capital to place, and by tying caps (concentration and TVL-share) to their effect on output, though it does not restate units or bounds itself.

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+resource ('Plan a hire of the ChainHelix yieldopt agent'), names the agent by ERC-8004 id, and defines its domain ('Yield allocation across pools'). That implicitly separates it from sibling planners (gridtrader, rebalancer, healthmon) without naming any of them explicitly, so differentiation is inferred rather than spelled out.

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?

Lays out the workflow clearly: send parameters, receive a live signed quote plus createJob calldata, then fund from your own wallet and notify the agent ('steps in the answer'). Adds a useful cost cue ('This call is free; the job is not'). It never contrasts with hire_quote or the other hire_plan_* planners, so no explicit exclusions.

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