Bitview

Bulk series data

get_series_bulk

Read-onlyIdempotent

Fetch multiple series in a single request. Supports filtering by index and date range. Returns an array of SeriesData objects. For a single series, use get_series instead.

REST operation: GET /api/series/bulk.

Input Schema

Name	Required	Description
`end`	No	Exclusive end: integer index, date (YYYY-MM-DD), or timestamp (ISO 8601). Negative integers count from end.
`index`	Yes
`limit`	No	Maximum number of values to return; with `end` too, the tighter of the two applies. Omitted, the rest of the range.
`start`	No	Inclusive start: integer index, date (YYYY-MM-DD), or timestamp (ISO 8601). Negative integers count from end.
`format`	No
`series`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed25 schema fields changedOct 30, 2026

removedInput schema / $defs / Format / description

Removed value: -"Output format for API responses"

changedInput schema / $defs / Index / description

Previous 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."

changedInput schema / $defs / Index / enum

Previous 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"
+]

changedInput schema / $defs / Limit / description

Previous value: -"Maximum number of results to return. Defaults to 100 if not specified."New value: +"Maximum number of results to return; each parameter states what omitting it means."

removedInput schema / $defs / Limit / format
```
Removed value: -"uint"
```

changedInput schema / $defs / RangeIndex / anyOf

Previous value: -[
-  {
-    "examples": [
-      0,
-      -366
-    ],
-    "format": "int64",
-    "type": "integer"
-  },
-  {
-    "examples": [
-      "2025-08-15"
-    ],
-    "format": "date",
-    "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
-    "type": "string"
-  },
-  {
-    "examples": [
-      "2025-08-15T00:00:00Z"
-    ],
-    "format": "date-time",
-    "type": "string"
-  }
-]New value: +[
+  {
+    "examples": [
+      0,
+      -366
+    ],
+    "type": "integer"
+  },
+  {
+    "examples": [
+      "2025-08-15"
+    ],
+    "format": "date",
+    "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+    "type": "string"
+  },
+  {
+    "examples": [
+      "2025-08-15T00:00:00Z"
+    ],
+    "format": "date-time",
+    "type": "string"
+  }
+]

changedInput schema / $defs / SeriesList / description

Previous value: -"Comma-separated list of series names"New value: +"Comma-separated list of series names\n\nDeserialization permits at most 32 normalized names and 2,048 decoded input\nstring bytes. For arrays, the byte budget is shared by their string values."

addedInput schema / $defs / SeriesList / maxLength
```
Added value: +2048
```

changedInput schema / properties / end / description

Previous value: -"Exclusive end: integer index, date (YYYY-MM-DD), or timestamp (ISO 8601). Negative integers count from end. Aliases: `to`, `t`, `e`"New value: +"Exclusive end: integer index, date (YYYY-MM-DD), or timestamp (ISO 8601). Negative integers count from end."

removedInput schema / properties / format / description
```
Removed value: -"Format of the output"
```
removedInput schema / properties / index / description
```
Removed value: -"Index to query"
```

changedInput schema / properties / limit / description

Previous value: -"Maximum number of values to return (ignored if `end` is set). Aliases: `count`, `c`, `l`"New value: +"Maximum number of values to return; with `end` too, the tighter of the two applies. Omitted, the rest of the range."

removedInput schema / properties / series / description
```
Removed value: -"Requested series"
```

changedInput schema / properties / start / description

Previous value: -"Inclusive start: integer index, date (YYYY-MM-DD), or timestamp (ISO 8601). Negative integers count from end. Aliases: `from`, `f`, `s`"New value: +"Inclusive start: integer index, date (YYYY-MM-DD), or timestamp (ISO 8601). Negative integers count from end."

changedOutput schema / $defs / Index / enum

Previous 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"
+]

removedOutput schema / $defs / SeriesData / properties / end / format
```
Removed value: -"uint"
```
addedOutput schema / $defs / SeriesData / properties / index / $ref
```
Added value: +"#/$defs/Index"
```
removedOutput schema / $defs / SeriesData / properties / index / allOf
```
Removed value: -[
-  {
-    "$ref": "#/$defs/Index"
-  }
-]
```
removedOutput schema / $defs / SeriesData / properties / stamp
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / $defs / SeriesData / properties / start / format
```
Removed value: -"uint"
```
removedOutput schema / $defs / SeriesData / properties / version / allOf
```
Removed value: -[
-  {
-    "$ref": "#/$defs/Version"
-  }
-]
```
addedOutput schema / $defs / SeriesData / properties / version / minimum
```
Added value: +0
```
addedOutput schema / $defs / SeriesData / properties / version / type
```
Added value: +"integer"
```

changedOutput schema / $defs / SeriesData / required

Previous value: -[
-  "version",
-  "index",
-  "start",
-  "end",
-  "stamp",
-  "data"
-]New value: +[
+  "version",
+  "index",
+  "start",
+  "end",
+  "data"
+]

removedOutput schema / $defs / Version

Removed value: -{
-  "format": "uint32",
-  "minimum": 0,
-  "type": "integer"
-}

First observedOct 23, 2026

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds the return shape ('array of SeriesData objects') and the underlying REST operation, which is useful context beyond the annotations, though it doesn't mention pagination or error behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences plus the REST line; the core purpose and the sibling routing are front-loaded with no wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

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 needn't be explained, and the description correctly signals the array-of-SeriesData result. The remaining gap is parameter-level guidance for the series list and limit interplay, which the 50% schema coverage doesn't fully cover.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%, so the description needs to compensate. It gestures at 'filtering by index and date range' (start/end/index) but says nothing about the comma-separated `series` list format, its 32-name/2048-byte budget, `limit`, or `format` — all left to the schema. Adequate but leaves a gap at this coverage level.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Fetch multiple series in a single request') and explicitly contrasts with the sibling get_series for single-series use. An agent can distinguish this bulk variant from get_series without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes single-series callers to `get_series` instead, which is a concrete alternative. It doesn't spell out other exclusion conditions (e.g., when to prefer get_series_latest or search_series), but the primary branching decision is stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Bitview tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.