Bullrun

Get ETF time series

get_etf_timeseries

Read-only

Fetch ETF price or price-return history at daily, weekly, or monthly intervals. NAV, true total-return, benchmark, and premium/discount series are returned only when their required source data or an explicit benchmark ticker exists; unavailable requested series are named explicitly and never approximated with price returns. Read-only.

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum recent daily source bars to load before date filtering and interval aggregation.
`series`	No	Requested series. Unsupported stored series are reported in unavailableSeries rather than synthesized.
`ticker`	Yes	Exact Bullrun ETF listing ticker.
`endDate`	No
`interval`	No		daily
`startDate`	No
`benchmarkTicker`	No	Exact priced ticker to use when benchmark is requested. A benchmark name alone cannot resolve a price series safely.

Output Schema

Name	Required	Description	Default
`series`	Yes
`ticker`	Yes
`webPage`	No
`interval`	Yes
`metadata`	Yes
`warnings`	Yes
`platformLink`	No
`availableSeries`	Yes
`requestedSeries`	Yes
`unavailableSeries`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 22, 2026
- removedOutput schema / properties / availableSeries / items / $ref
```
Removed value: -"#/properties/requestedSeries/items"
```
- addedOutput schema / properties / availableSeries / items / enum
```
Added value: +[
+  "price",
+  "price_return",
+  "nav",
+  "total_return",
+  "benchmark",
+  "premium_discount"
+]
```
- addedOutput schema / properties / availableSeries / items / type
```
Added value: +"string"
```
- removedOutput schema / properties / unavailableSeries / items / $ref
```
Removed value: -"#/properties/requestedSeries/items"
```
- addedOutput schema / properties / unavailableSeries / items / enum
```
Added value: +[
+  "price",
+  "price_return",
+  "nav",
+  "total_return",
+  "benchmark",
+  "premium_discount"
+]
```
- addedOutput schema / properties / unavailableSeries / items / type
```
Added value: +"string"
```

Changed2 schema fields changedOct 12, 2026

addedOutput schema / properties / platformLink

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "description": {
+      "type": "string"
+    },
+    "label": {
+      "type": "string"
+    },
+    "url": {
+      "format": "uri",
+      "type": "string"
+    }
+  },
+  "required": [
+    "label",
+    "url",
+    "description"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / webPage

Added value: +{
+  "format": "uri",
+  "type": "string"
+}

AddedAug 11, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description still adds real behavioral value: unavailable requested series are named in unavailableSeries and are never silently approximated with price returns, and series availability has prerequisites. Return shape details (e.g. unavailableSeries structure) are left to 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.

Conciseness4/5

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

Two dense sentences, front-loaded with the core capability followed by the availability caveat. The trailing 'Read-only.' merely restates the readOnlyHint annotation and is the one sentence that does not earn its place.

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?

For a read-only fetch with an output schema (so return values need no prose) and explicit child-series caveats, this is nearly complete. Minor omission is how limit interacts with interval aggregation and date filtering, which matters for a 7-parameter tool.

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?

With 57% schema coverage, the description compensates for the weakest spots: it explains that benchmark requires an explicit priced benchmarkTicker because a benchmark name cannot resolve to a price series, and it clarifies series availability semantics. It says nothing about how limit interacts with interval aggregation or about startDate/endDate beyond their pattern, leaving gaps.

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 ('Fetch ETF price or price-return history') plus the supported intervals, which immediately separates it from snapshot/exposure siblings. It never names a sibling such as get_etf_snapshot or get_stock_price_history to draw the boundary explicitly, so it stops short of 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 the name and the series/interval framing, and the description does explain the conditional rule that NAV/total-return/benchmark series only appear when source data or an explicit benchmarkTicker exists. However, it gives no when-to-use vs when-not guidance and never points to an alternative tool.

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

All Bullrun 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.