The instrument list of the ChainHelix instrument lane: SpaceX and Circle perpetuals on Aster (BNB Chain). Venue, contract, chain, fees, funding cycle, session policy and the label every answer uses. These are derivatives on the venue, never the share
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| product | No | ||
| namespace | No | ||
| instruments | No |
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-lexiconAdded value: +{
+ "bundleSha256": "c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4",
+ "name": "ChainHelix Agentic Lexicon",
+ "resolve": "lexicon_resolve",
+ "spec": "lexicon_spec",
+ "version": "0.1.0"
+}Input schema / x-vocabAdded value: +{}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It does disclose the content shape (venue, contract, chain, fees, funding cycle, session policy, label) and adds a useful scoping note that these are derivatives on the venue, never the share. However it says nothing about permissions, freshness, or read semantics.
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?
Two sentences, front-loaded with the resource, with no filler. The second sentence about derivatives-not-shares earns its place as a scoping clarification, though the jargon-heavy phrasing is slightly dense.
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?
A zero-parameter listing tool with an output schema and no annotations. The description covers what the list contains and the nature of the instruments, and the output schema carries return-value detail, so little is missing for correct invocation.
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?
The tool takes zero parameters (empty schema, additionalProperties false), so there are no parameter semantics to document. Baseline 4 applies; nothing in the description contradicts the schema.
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 resource (the ChainHelix instrument lane) and enumerates exactly what it covers: SpaceX and Circle perpetuals on Aster (BNB Chain). An agent can tell it is a listing tool, distinct from siblings like instrument_signals or instrument_state, though those siblings are never named explicitly.
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?
There is no when-to-use, when-not-to-use, or alternative routing guidance. Given a dense cluster of instrument_* siblings (signals, spec, state), the description should say when to reach for the list versus those, but it leaves that entirely to inference.
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.