Skip to main content
Glama

intel

by io.chainhelix
OverviewDiscussionsAdmin

buy_key

Buy a ChainHelix API key without a browser or account. Pick a plan (standard 99 dollars a month at 120 requests per minute, or pro 249 dollars a month at 600 requests per minute) and a payment chain (ethereum, solana, bnb, polygon, tron, avalanche or sui). Returns a payment address, an exact amount in USDC or USDT, and a claim token. Send the exact amount, then call claim_key. Orders expire after 24 hours, or sooner under load (2 hours when more than 25 orders are open, 30 minutes above 40). Email is required for the alerts plan (Telegram delivery) and optional otherwise; with one, the key and receipt are also emailed

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
planYes
chainYes
emailNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

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: +{
+  "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"
+}
  5. 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"
+}
  6. Added

TDQS

A4.8/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 the returned artifacts (payment address, exact USDC/USDT amount, claim token), the expiring-order behavior with load-dependent time windows, and email-delivery side effects. An agent can predict the tool's effects beyond the call itself.

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 front-loaded with the core buy action, then parameters, then follow-up workflow and constraints. The expiration and email details are dense but all earn their place; there is no filler or repetition.

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 three-parameter purchase flow with no annotations, the description is complete: it covers required parameters, optional conditions, return values, the next step (claim_key), and order expiry behavior. The agent has everything needed to invoke the tool correctly and continue the workflow.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description has to compensate, and it does thoroughly. It explains the plan values with prices and rate limits, lists the payment chain options, and clarifies the conditional email requirement. This adds substantial meaning beyond the bare enum names and property types.

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: 'Buy a ChainHelix API key without a browser or account.' It then states the plan and payment chain choices and what the tool returns. It is clearly distinguishable from the sibling claim_key because it explicitly names claim_key as the next step.

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 a concrete usage context: purchase happens without a browser or account, then 'Send the exact amount, then call claim_key.' It does not explicitly say when not to use the tool or mention key_order_status as an alternative, but the workflow guidance is clear and actionable.

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