Skip to main content
Glama

Bullrun

by org.bull-run
OverviewDiscussionsAdmin

Query ETFs

query_etfs
Read-only

Compatibility tool for older clients: search the Bullrun ETF universe and optionally bundle profile, recent prices, and latest holdings for an exact ticker. New clients should use search_etfs, get_etf_snapshot, and get_etf_holdings for smaller responses, structured output, quantitative filters, and explicit coverage metadata. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
focusNoExact ETF exposure filter, such as Japan, Equity - Australia, TOPIX, or an exchange/source exposure label. Kept as focus for API compatibility.
limitNoMaximum ETF search rows to return, 1-100.
searchNoFree-text ETF search by ticker or fund name. Omit to list the first ETFs.
tickerNoExact ETF ticker for profile, prices, and optional holdings, e.g. SPY, VWRL.L, EUNL.DE.
categoryNoExact broad ETF asset-class filter, such as Equity, Fixed Income, Commodity, Crypto, or Real Estate. Kept as category for API compatibility.
currencyNoExact trading currency filter, e.g. USD, EUR, CHF.
domicileNoExact ETF domicile filter.
exchangeNoExact exchange filter, e.g. NYSE ARCA, LSE, XETRA.
priceLimitNoRecent daily price rows to return for an exact ticker. Use 0 to skip prices.
holdingsLimitNoMaximum holdings to return for an exact ticker, 1-100.
includeHoldingsNoWhen ticker is supplied, include latest holdings. Ignored for broad searches.
includeInactiveNoInclude ETFs with no recent price bar. Default false.
includeSecondaryNoInclude secondary/cross-listed ETF tickers. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Exact ETF category filter. This maps to Bullrun's ETF category column."New value: +"Exact broad ETF asset-class filter, such as Equity, Fixed Income, Commodity, Crypto, or Real Estate. Kept as category for API compatibility."
    • changedInput schema / properties / focus / description
      Previous value: -"Exact ETF focus filter. This maps to Bullrun's ETF focus / asset-class column."New value: +"Exact ETF exposure filter, such as Japan, Equity - Australia, TOPIX, or an exchange/source exposure label. Kept as focus for API compatibility."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds useful context about legacy compatibility and the bundled response for exact tickers. However, it does not mention potential performance implications or error behavior, which would be valuable for a tool intended for older clients.

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?

The description is succinct and front-loaded with purpose and alternatives. The final 'Read-only' sentence is redundant with the annotations and could be omitted without loss, but the overall structure is tight.

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 13-parameter compatibility tool with no output schema, the description gives the essential context: legacy purpose, search scope, optional bundled data, and modern alternatives. It does not describe response structure or edge cases, but the parameter schema covers the input details thoroughly.

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%, so the schema already documents every parameter in detail. The description adds some context by explaining the bundling relationship between ticker, prices, and holdings, but this is also hinted at in the individual parameter descriptions.

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?

The description explicitly states it is a compatibility tool for older clients that searches the Bullrun ETF universe and can bundle profile, prices, and holdings for a ticker. It also distinguishes itself by naming the newer alternative tools.

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

Usage Guidelines5/5

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

It explicitly advises new clients to use search_etfs, get_etf_snapshot, and get_etf_holdings, listing specific benefits of those alternatives (smaller responses, structured output, quantitative filters, explicit coverage metadata). This gives clear when-to-use vs. when-not-to-use guidance.

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

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

Resources