Bitview

Series list

list_series

Read-onlyIdempotent

Paginated flat list of all available series names.

REST operation: GET /api/series/list.

Input Schema

Name	Required	Description	Default
`page`	No	Zero-based page number (default: 0)
`per_page`	No	Results per page, 1 to 1,000 (default: 1000)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedOct 30, 2026
- addedInput schema / properties / page / default
```
Added value: +0
```
- changedInput schema / properties / page / description
```
Previous value: -"Pagination index"New value: +"Zero-based page number (default: 0)"
```
- removedInput schema / properties / page / format
```
Removed value: -"uint"
```
- addedInput schema / properties / per_page / default
```
Added value: +1000
```
- changedInput schema / properties / per_page / description
```
Previous value: -"Results per page (default: 1000, max: 1000)"New value: +"Results per page, 1 to 1,000 (default: 1000)"
```
- removedInput schema / properties / per_page / format
```
Removed value: -"uint"
```
- addedInput schema / properties / per_page / maximum
```
Added value: +1000
```
- changedInput schema / properties / per_page / minimum
```
Previous value: -0New value: +1
```
- removedOutput schema / $defs / PaginatedSeries / properties / current_page / format
```
Removed value: -"uint"
```
- removedOutput schema / $defs / PaginatedSeries / properties / max_page / format
```
Removed value: -"uint"
```
- removedOutput schema / $defs / PaginatedSeries / properties / per_page / format
```
Removed value: -"uint"
```
- addedOutput schema / $defs / PaginatedSeries / properties / series / items / $ref
```
Added value: +"#/$defs/SeriesName"
```
- removedOutput schema / $defs / PaginatedSeries / properties / series / items / type
```
Removed value: -"string"
```
- removedOutput schema / $defs / PaginatedSeries / properties / total_count / format
```
Removed value: -"uint"
```
- addedOutput schema / $defs / SeriesName
```
Added value: +{
+  "pattern": "^[a-z0-9_]+$",
+  "type": "string"
+}
```
First observedOct 23, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds that the list is unfiltered/flat (implying a full enumeration) and pins the REST endpoint, but says nothing about response size risk despite a default per_page of 1000, or ordering of results.

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

Conciseness4/5

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

Two short sentences with the core statement front-loaded and no filler. The REST endpoint line is compact and useful for callers mapping to the underlying API.

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

Completeness3/5

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 explained, and annotations cover safety. Still missing is any clarification of how this differs from the many get_series*/search_series siblings and any warning that the default page size of 1,000 can produce a very large payload.

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 description coverage is 100%, with both page and per_page fully documented including defaults, ranges, and examples. The description only repeats 'paginated' and adds no semantics beyond the schema, so the baseline 3 is appropriate.

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

Purpose4/5

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

States a specific verb and resource: a paginated flat list of all available series names. The word 'flat' and 'names' signal that this returns identifiers only, not data points, which distinguishes it somewhat from get_series. However, it never explicitly names the closely-related siblings (get_series, get_series_info, search_series) it differs from.

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

Usage Guidelines2/5

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

No when-to-use guidance is given. With siblings like search_series, get_series, get_series_info, get_series_bulk, and get_series_latest available, the agent must infer from the name alone that this is for enumerating the full series catalogue rather than searching or fetching values. No exclusions or alternatives are named.

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.