Bullrun

Get ETF snapshot

get_etf_snapshot

Read-only

Fetch a modular snapshot for one exact ETF listing. The include array controls which of identity, classification, market, fund_data (NAV/AUM), costs, income, and benchmark are fetched and returned. Unrequested modules are omitted; requested-but-unavailable modules are named explicitly. Ratios use percentage points. Read-only.

Input Schema

Name	Required	Description	Default
`ticker`	Yes	Exact Bullrun ETF listing ticker, including its exchange suffix when present, e.g. SPY, VWRL.L, or EUNL.DE.
`include`	No	Only these snapshot modules are fetched and returned. Default: identity, classification, market, costs.

Output Schema

Name	Required	Description	Default
`asOf`	Yes
`found`	Yes
`ticker`	Yes
`modules`	Yes
`webPage`	No
`dataQuality`	Yes
`platformLink`	No
`missingModules`	Yes
`availableModules`	Yes
`requestedModules`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 22, 2026
- removedOutput schema / properties / availableModules / items / $ref
```
Removed value: -"#/properties/requestedModules/items"
```
- addedOutput schema / properties / availableModules / items / enum
```
Added value: +[
+  "identity",
+  "classification",
+  "market",
+  "fund_data",
+  "costs",
+  "income",
+  "benchmark"
+]
```
- addedOutput schema / properties / availableModules / items / type
```
Added value: +"string"
```
- removedOutput schema / properties / missingModules / items / $ref
```
Removed value: -"#/properties/requestedModules/items"
```
- addedOutput schema / properties / missingModules / items / enum
```
Added value: +[
+  "identity",
+  "classification",
+  "market",
+  "fund_data",
+  "costs",
+  "income",
+  "benchmark"
+]
```
- addedOutput schema / properties / missingModules / 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.9/5.0

Behavior4/5

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

Annotations already cover read-only/non-destructive/closed-world, yet the description adds genuinely new behavior: unrequested modules are omitted while requested-but-unavailable modules are named explicitly, and ratios are reported in percentage points. The closing "Read-only." merely restates readOnlyHint=true, so it earns no credit and slightly dilutes the value.

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?

Four short sentences, front-loaded with the core action and scope, and each sentence adds a distinct fact except the trailing "Read-only." which duplicates the annotation. Slight redundancy keeps it just below the top mark.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with an output schema, full schema coverage, and annotations covering safety and openness, the description supplies everything else needed: scope, module semantics, omission/availability behavior, and unit conventions for the returned numbers.

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 baseline is 3; the description goes beyond it by explaining the include array as a fetch-and-return filter and by stating the percentage-point unit convention, which is data semantics the schema does not carry. Ticker precision is left entirely to the schema example, which is acceptable.

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?

"Fetch a modular snapshot for one exact ETF listing" gives a specific verb and resource, and the word "modular" plus the module list distinguishes it from bulk/comparison siblings. It stops short of naming the adjacent single-ETF siblings (get_etf_fund, get_etf_holdings, get_etf_risk) that an agent would need to choose between.

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 "one exact ETF listing" (single-entity lookup, not screening/comparison), but there is no explicit when-to-use or when-not-to-use guidance and no alternative named among the many ETF siblings. An agent can infer a rough fit but must still reason about overlap with get_etf_fund and get_etf_exposures.

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.