get_series_versionReturns the vector's schema/computation version, not its length or latest update. Appends and reorgs do not by themselves change this version.
REST operation: GET /api/series/{series}/{index}/version.
| Name | Required | Description | Default |
|---|---|---|---|
| index | Yes | ||
| series | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Input schema / $defs / Index / descriptionPrevious value: -"Aggregation dimension for querying series. Includes time-based (date, week, month, year),\nblock-based (height, tx_index), and address/output type indexes."New value: +"Aggregation dimension for querying series. Includes time-based (date, week, month, year), block-based (height, tx_index), and address/output type indexes."Input schema / $defs / Index / enumPrevious value: -[
- "minute10",
- "minute30",
- "hour1",
- "hour4",
- "hour12",
- "day1",
- "day3",
- "week1",
- "month1",
- "month3",
- "month6",
- "year1",
- "year10",
- "halving",
- "epoch",
- "height",
- "tx_index",
- "txin_index",
- "txout_index",
- "empty_output_index",
- "op_return_index",
- "p2a_addr_index",
- "p2ms_output_index",
- "p2pk33_addr_index",
- "p2pk65_addr_index",
- "p2pkh_addr_index",
- "p2sh_addr_index",
- "p2tr_addr_index",
- "p2wpkh_addr_index",
- "p2wsh_addr_index",
- "unknown_output_index",
- "funded_addr_index",
- "empty_addr_index",
- "extended_empty_addr_index"
-]New value: +[
+ "minute10",
+ "minute30",
+ "hour1",
+ "hour4",
+ "hour12",
+ "day1",
+ "day3",
+ "week1",
+ "month1",
+ "month3",
+ "month6",
+ "year1",
+ "year10",
+ "halving_epoch",
+ "difficulty_epoch",
+ "height",
+ "tx_index",
+ "txin_index",
+ "txout_index",
+ "empty_script_output_index",
+ "op_return_output_index",
+ "p2a_address_index",
+ "p2ms_output_index",
+ "p2pk33_address_index",
+ "p2pk65_address_index",
+ "p2pkh_address_index",
+ "p2sh_address_index",
+ "p2tr_address_index",
+ "p2wpkh_address_index",
+ "p2wsh_address_index",
+ "unknown_script_output_index"
+]Input schema / $defs / SeriesName / descriptionRemoved value: -"Series name"Input schema / $defs / SeriesName / patternAdded value: +"^[a-z0-9_]+$"Input schema / properties / index / descriptionRemoved value: -"Aggregation index"Input schema / properties / series / descriptionRemoved value: -"Series name"Output schema / $defs / Version / formatRemoved value: -"uint32"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover read-only, idempotent, open-world, and non-destructive behavior. The description adds useful semantics beyond that: appends and reorgs do not by themselves change this version, which helps the agent understand what the returned version represents.
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 description is front-loaded with the key distinction, explains the meaning of the version in one additional sentence, and ends with the REST operation. There is no wasted text.
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 described. The description adequately explains the tool's semantic purpose and behavioral nuance, but it leaves parameter meaning largely to the schema despite low documented coverage.
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 reported as 0%, and the description does not explain what series or index mean semantically beyond showing them in the REST path. It relies entirely on the schema's examples and enum to convey parameter meaning, leaving a significant gap for two required parameters.
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 precise verb and resource: it returns the vector's schema/computation version. It also distinguishes this from sibling concepts like length and latest update, so an agent can separate it from get_series_len and get_series_latest.
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 clearly frames when this tool is appropriate by contrast: use it for schema/computation version, not for length or latest update. However, it does not explicitly name the alternative sibling tools or state exclusions beyond those contrasts.
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.