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 | Claim token of the order, 32 hex characters. Example: 5f2c9a0e1b7d4c3a8e6f0b1d2c3e4f5a |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Input schema / properties / claim_token / descriptionAdded value: +"Claim token of the order, 32 hex characters. Example: 5f2c9a0e1b7d4c3a8e6f0b1d2c3e4f5a"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?
readOnlyHint=true is consistent with 'check' and 'reports'. The description adds real behavioral detail beyond annotations: the two status facts returned (payment seen, key ready to claim). It does not cover error behavior for an unknown/expired token, so it does not earn a 4.
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?
The front-loaded sentence is self-defeating: it announces there is no order to check and then instructs the agent to check an order. Three sentences for one parameter, with internal redundancy and no clear lead statement of what the tool does.
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?
With an output schema present, return values need not be spelled out, and the description does sketch the two reported facts. What is missing is the token lifecycle context: what a claim token represents, and what an agent should do if the check fails.
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 coverage is 100% and the single claim_token parameter is fully documented (32 hex characters, example). The description only restates 'takes the claim token' with no added semantics, so the baseline 3 applies.
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 second sentence gives a specific verb and resource: check a key order created with buy_key, reporting payment-seen and claim-readiness. However, the opening sentence ('keys are not on sale... there is no order to check') directly muddles that purpose, leaving the agent unsure whether the tool is usable 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 names buy_key as the creating tool and states a when-not condition (no orders currently exist), which is genuinely useful routing context. But the two statements conflict, and it never tells the agent what to do instead when an order is absent.
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.