Claim the API key for a paid buy_key order. Takes the claim token. The key is returned exactly once, save it. Payments usually become claimable within 30 minutes of confirming on chain
| Name | Required | Description | Default |
|---|---|---|---|
| claim_token | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Input schema / x-lexicon / bundleSha256Previous value: -"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"New value: +"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"Input schema / x-lexicon / bundleSha256Previous value: -"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"New value: +"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"Input schema / x-lexicon / bundleSha256Previous value: -"c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4"New value: +"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"Input schema / x-aliasesAdded value: +{
+ "claim_token": [
+ "claimToken"
+ ]
+}Input schema / x-lexiconAdded value: +{
+ "bundleSha256": "c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4",
+ "name": "ChainHelix Agentic Lexicon",
+ "resolve": "lexicon_resolve",
+ "spec": "lexicon_spec",
+ "version": "0.1.0"
+}Input schema / x-vocabAdded value: +{
+ "claim_token": "agent.claimToken"
+}Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": true,
+ "description": "the issued key for a paid order, once",
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full behavioral burden. It discloses the critical exactly-once behavior ('The key is returned exactly once, save it') and the expected claimable timing. It doesn't address repeated-claim consequences or auth requirements, but the disclosed details are highly valuable and non-obvious.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences, each earning its place: purpose, critical usage detail, and timing expectation. The most important action is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter tool with an output schema present, the description covers the action, parameter, critical result behavior, and timing. It is sufficiently complete, though it could add a pointer to key_order_status when keys are not yet claimable.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate for the undocumented parameter. It only says 'Takes the claim token,' which essentially restates the parameter name and adds little detail about where the token comes from, its format, or how to handle missing/invalid tokens.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Claim'), a specific resource ('the API key'), and a clear relationship to 'a paid buy_key order.' This immediately distinguishes the tool from siblings like buy_key (purchase action) and key_order_status (status check).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear usage context: it should be used for a paid buy_key order, requires a claim token, and the agent should expect payments to become claimable within ~30 minutes of chain confirmation. It does not explicitly name alternatives or exclusions, so it stops short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.