Bitview

Search series

search_series

Read-onlyIdempotent

Search series by name or descriptive terms. Results prioritize whole query words in names, then descriptions, then fuzzy names, then fuzzy descriptions. Word order does not matter. Descriptions provide cohort terminology and formulas. The decoded q parameter is limited to 1024 UTF-8 bytes.

REST operation: GET /api/series/search.

Input Schema

Name	Required	Description	Default
`q`	Yes	Words to find in series names and descriptions (`realized price`, `mvrv`), in any order
`limit`	No	Maximum number of results, 1 to 1,000 (default: 100)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedOct 30, 2026

removedInput schema / $defs

Removed value: -{
-  "Limit": {
-    "description": "Maximum number of results to return. Defaults to 100 if not specified.",
-    "examples": [
-      1,
-      10,
-      100
-    ],
-    "format": "uint",
-    "minimum": 0,
-    "type": "integer"
-  },
-  "SeriesName": {
-    "description": "Series name",
-    "examples": [
-      "price_close",
-      "market_cap",
-      "realized_price"
-    ],
-    "type": "string"
-  }
-}

removedInput schema / properties / limit / $ref
```
Removed value: -"#/$defs/Limit"
```
addedInput schema / properties / limit / default
```
Added value: +100
```

changedInput schema / properties / limit / description

Previous value: -"Maximum number of results"New value: +"Maximum number of results, 1 to 1,000 (default: 100)"

addedInput schema / properties / limit / examples
```
Added value: +[
+  10,
+  100
+]
```
addedInput schema / properties / limit / maximum
```
Added value: +1000
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```
addedInput schema / properties / limit / type
```
Added value: +"integer"
```
removedInput schema / properties / q / $ref
```
Removed value: -"#/$defs/SeriesName"
```

changedInput schema / properties / q / description

Previous value: -"Search query string"New value: +"Words to find in series names and descriptions (`realized price`, `mvrv`), in any order"

addedInput schema / properties / q / examples
```
Added value: +[
+  "realized price"
+]
```
addedInput schema / properties / q / type
```
Added value: +"string"
```

addedOutput schema / $defs

Added value: +{
+  "SeriesName": {
+    "pattern": "^[a-z0-9_]+$",
+    "type": "string"
+  }
+}

addedOutput schema / items / $ref
```
Added value: +"#/$defs/SeriesName"
```
removedOutput schema / items / type
```
Removed value: -"string"
```

First observedOct 23, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds useful behavioral detail beyond annotations: result ranking order, word-order insensitivity, and the 1024-byte decoded q constraint. Return-value behavior is covered by the output schema.

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?

The description is compact and front-loaded: purpose first, then ranking behavior, then a key constraint. Every sentence contributes relevant information for selecting or invoking the tool.

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 rich annotations, 100% schema description coverage, and an output schema, the description supplies enough context to invoke the tool correctly. Its main remaining gap is not explicitly routing between this search tool and sibling series-list/get tools.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already defines both parameters well. The description adds meaningful parameter context by stating that word order does not matter and that the decoded q parameter is limited to 1024 UTF-8 bytes, which is not captured in the schema.

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?

The description states a specific verb and resource: search series by name or descriptive terms. It also explains ranking behavior, making the operation clear. It does not explicitly differentiate itself from the sibling list_series tool, which keeps it from a 5.

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

Usage Guidelines3/5

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

Usage is implied by 'search series by name or descriptive terms,' but the description does not state when to use this instead of list_series or get_series. No alternatives or exclusions are named, leaving the agent to infer the selection context.

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.