Bullrun

Screen ETFs

screen_etfs

Read-only

Screen the WHOLE ETF universe by numeric rules and fund attributes in one pass — expense ratio, AUM, yield, trailing returns, volatility, liquidity, top-10 concentration, fund age and holdings count — combined with issuer, index, domicile, UCITS status, distribution policy, currency hedging and constituent look-through (holdingSearch finds funds by what they hold). Prefer this over search_etfs for any "cheapest / largest / best performing / most liquid" question: search_etfs only filters a bounded candidate scan, while this evaluates the full universe and reports evaluatedCount and matchCount. Percentages are percentage points. This full-universe screen is an expensive read, and request limits depend on your connection and plan. Build one precise screen to conserve your allowance. Read-only.

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum ETFs to return, 1-100.
`order`	No	Sort direction. Nulls always sort last regardless of direction.	desc
`rules`	No	Numeric rules. A fund with no value for a ruled metric never matches that rule.
`issuer`	No	Substring match on the fund family/issuer, e.g. "iShares", "Amundi", "Vanguard".
`region`	No	Exact investment-region string.
`search`	No	Free-text match on ticker, fund name or ISIN. Omit to screen the whole universe.
`sortBy`	No	Sort field applied to the returned rows.	totalAssets
`category`	No	Exact category string. Call get_etf_filter_options for the valid values; a wrong guess silently returns zero rows.
`currency`	No	Exact trading currency, e.g. EUR, USD, GBX.
`domicile`	No	Exact fund domicile, e.g. "Ireland", "Luxembourg", "United States".
`exchange`	No	Exact listing exchange, e.g. XETRA, LSE, "NYSE ARCA".
`indexKey`	No	Exact tracked-index key, e.g. SP500, MSCI_WORLD, NASDAQ100. Use get_etf_index_group to compare every fund on one index instead.
`strategy`	No	Exact strategy classification string.
`assetClass`	No	Exact asset-class group: EQUITY, FIXED_INCOME, COMMODITY, REAL_ESTATE, MULTI_ASSET, CASH, CURRENCY, DIGITAL_ASSETS, ALTERNATIVES or OTHER.
`holdingMode`	No	INCLUDES keeps funds holding the constituent. EXCLUDES keeps only funds with a holdings snapshot that confirms absence — funds with no snapshot are dropped, never assumed clean.	INCLUDES
`productType`	No	Exact wrapper type, e.g. UCITS_FUND.
`ucitsStatus`	No	UCITS restricts to wrappers a European retail investor can actually buy.
`holdingSearch`	No	Look-through filter: find funds by a CONSTITUENT ticker or company name, e.g. "NVDA" or "NVIDIA". Only funds with a stored holdings snapshot can match.
`currencyHedged`	No	HEDGED selects funds labelled currency-hedged. NOT_LABELLED_HEDGED selects funds not so labelled — absence of a label is not proof a fund is unhedged.
`benchmarkSearch`	No	Substring match on the stated benchmark name.
`includeSecondary`	No	Return every venue listing as its own row. Default false: one row per FUND (by fund ISIN), showing its most liquid listing with the others under otherListings. Use exchange/currency to choose the venue, e.g. exchange "SW" for the SIX line.
`marketDevelopment`	No	Exact market-development classification, e.g. developed vs emerging.
`distributionPolicy`	No	Accumulating (reinvests income) or distributing (pays it out) — the usual first cut for a European investor.
`holdingMinWeightPct`	No	Minimum constituent weight in percentage points for holdingSearch to count as a match.

Output Schema

Name	Required	Description	Default
`query`	Yes
`results`	Yes
`webPage`	No
`coverage`	Yes
`returned`	Yes
`warnings`	Yes
`matchCount`	Yes
`platformLink`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 19, 2026

changedInput schema / properties / includeSecondary / description

Previous value: -"Include secondary venue listings of the same fund. Default false — one row per fund's primary listing."New value: +"Return every venue listing as its own row. Default false: one row per FUND (by fund ISIN), showing its most liquid listing with the others under otherListings. Use exchange/currency to choose the venue, e.g. exchange \"SW\" for the SIX line."

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 17, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already establish that the tool is read-only, non-destructive, and closed-world. The description adds valuable behavioral context beyond annotations: the screen is expensive, request limits depend on connection/plan, one precise screen should be built to conserve allowance, and the result reports evaluatedCount and matchCount. It does not detail output shape, but an output schema exists, so this is a minor gap.

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 front-loaded with the key differentiator and use case, then adds cost guidance and unit semantics. It is appropriately long for a 24-parameter screening tool, though the long attribute list and final "Read-only" repetition slightly reduce concision.

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?

Given the tool's complexity, 24 parameters, 100% schema description coverage, annotations, and an output schema, the description provides the crucial context: full-universe scope, alternative tool distinction, cost implications, and unit conventions. Nothing essential for correct invocation is missing from the description.

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 the 24 parameters thoroughly, making 3 the appropriate baseline. The description adds some useful global semantics, especially that percentages are percentage points and that holdingSearch matches funds by constituent holdings, but it does not meaningfully expand on parameter behavior beyond what the schema provides.

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 gives a specific verb and resource: screen the whole ETF universe by numeric rules and fund attributes. It lists the exact metric groups and attribute dimensions, and explicitly distinguishes this tool from search_etfs by full-universe evaluation versus bounded candidate scanning. An agent can identify the tool and its scope without opening the schema.

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 says to prefer this over search_etfs for "cheapest / largest / best performing / most liquid" questions and explains why: search_etfs only filters a bounded scan while this evaluates the full universe. It also notes that holdingSearch is a constituent look-through and that building one precise screen conserves allowance. This gives clear when-to-use and alternative selection guidance.

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.