Skip to main content
Glama
Sign In

ChainHelix for Machines

by io.chainhelix.mcp
OverviewDiscussionsAdmin

buy_key

API keys are not on sale at the moment: every plan answers "This plan is not on sale." and no order is created. When the sale opens this tool returns a payment address, an exact amount in a stablecoin the chosen chain accepts (ethereum, solana and avalanche: USDC or USDT; bnb: USDC, USDT, USD1 or U; polygon: USDC, USDT or USDC.e; tron: USDT; sui: USDC) and a claim token for the chosen plan and payment chain

Input Schema

NameRequiredDescriptionDefault
planYesPlan: standard, pro or alerts. Example: standard
chainYesPayment chain: ethereum, solana, bnb, polygon, tron, avalanche or sui. Example: bnb
emailNoEmail address for the key and receipt, required for the alerts plan. Example: ops@example.com

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / chain / description
      Added value: +"Payment chain: ethereum, solana, bnb, polygon, tron, avalanche or sui. Example: bnb"
    • addedInput schema / properties / email / description
      Added value: +"Email address for the key and receipt, required for the alerts plan. Example: ops@example.com"
    • addedInput schema / properties / plan / description
      Added value: +"Plan: standard, pro or alerts. Example: standard"
  2. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"670f7504e3de5031beccee25a2d24e4515f68b893295f6d5b0d3a0665498b2c9"New value: +"25cc80db6d8e9eac73d47a50f7ad6333a21f1972d008a8fed0159de8bfb4b519"
  3. 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"
  4. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  5. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"New value: +"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"
  6. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"New value: +"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"
  7. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4"New value: +"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"
  8. Changed3 schema fields changed
    • addedInput schema / x-aliases
      Added value: +{
+  "email": [
+    "Email",
+    "EMAIL"
+  ]
+}
    • 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: +{
+  "chain": "onchain.chain",
+  "email": "identity.email",
+  "plan": "payment.plan"
+}
  9. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "order terms for an API key: what to pay, where, and the order id to poll",
+  "type": "object"
+}
  10. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false), it discloses a non-obvious behavioral trait: today no order is created and the call effectively fails, and when a sale is live it issues payment address + claim token. It omits auth/permission requirements and whether repeated calls create duplicate orders.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The critical fact (not on sale) is front-loaded, which is good, but the second half is one long clause dense with parenthetical per-chain currency lists that is hard to parse. Several clauses could be tightened without losing information.

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?

With an output schema present and full schema coverage, the description needn't explain returns, yet it does describe address/amount/claim token, plus the current failure mode — enough for an agent to call it and interpret the result correctly.

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%, so the enum values are already documented; the description still adds real meaning by mapping each chain to its accepted stablecoins (bnb: USDC/USDT/USD1/U, tron: USDT, sui: USDC, etc.), which is not in the schema.

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 concrete verb and resource (buy an API key) and explains the artifact produced (payment address, exact stablecoin amount, claim token for the chosen plan/chain). It doesn't name a sibling like claim_key or key_order_status, so the boundary with those tools is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly establishes the current state (purchases are unavailable, every plan answers 'This plan is not on sale.') which tells an agent when NOT to expect success, but it never states when to prefer this over hire_quote, claim_key, or key_order_status.

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