API keys are not on sale at the moment and buy_key creates no order, so there is no order to check. Check a key order created with buy_key. Takes the claim token, reports whether the payment has been seen and whether the key is ready to claim
| 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: -"670f7504e3de5031beccee25a2d24e4515f68b893295f6d5b0d3a0665498b2c9"New value: +"25cc80db6d8e9eac73d47a50f7ad6333a21f1972d008a8fed0159de8bfb4b519"Input schema / x-lexicon / bundleSha256Previous value: -"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"New value: +"670f7504e3de5031beccee25a2d24e4515f68b893295f6d5b0d3a0665498b2c9"Input schema / x-lexicon / versionPrevious value: -"0.1.0"New value: +"0.2.0"Input schema / additionalPropertiesAdded value: +falseInput 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": "state of a key order: pending, paid, issued",
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It does disclose meaningful behavior beyond the schema: what the response conveys (whether payment was seen, whether the key is ready to claim) and an operational constraint (keys currently not on sale). It omits auth requirements, error behavior, and how long a payment takes to be observed, and its constraint statement conflicts with its own instruction.
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 with no padding, so length is fine. But the structure is front-loaded with a self-contradictory caveat that muddies the actual instruction, which should have led.
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?
An output schema exists, so return values need not be specified. For a single-parameter status tool the description is nearly adequate, but the internal contradiction about whether orders can exist leaves the agent without a reliable picture of when the tool is actionable.
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% for the single required claim_token, so the description must compensate. It only says 'Takes the claim token' and implies its origin is a buy_key purchase — useful but minimal; no format, length, or source-lookup guidance is given beyond that.
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 does state a specific verb and resource ('Check a key order created with buy_key') and what it reports. However, the leading sentence ('API keys are not on sale at the moment and buy_key creates no order, so there is no order to check') directly undercuts that purpose and leaves the agent unsure whether the tool can return anything meaningful at all.
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?
It ties the tool to buy_key ('created with buy_key'), which nominally identifies the prerequisite. But the same sentence says buy_key creates no order, so the guidance is self-cancelling: the agent is told to check orders that the description says cannot exist. No alternative or fallback is offered.
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.