Bullrun

Get ETF fund by ISIN

get_etf_fund

Read-only

Resolve one FUND rather than one listing. Given an ISIN (or any venue ticker of the fund) it returns the fund's identity, costs, index, distribution policy, wrapper type and every venue it is listed on with exchange and trading currency. Use this when the user quotes an ISIN, asks "which ticker do I buy on my exchange?", or when several tickers may be the same underlying fund. Ratios are percentage points. Read-only.

Input Schema

Name	Required	Description	Default
`isin`	No	Fund ISIN, e.g. IE00B4L5Y983. The identifier European factsheets and brokers quote.
`ticker`	No	Any venue listing ticker of the fund, e.g. EUNL.DE or IWDA.L. Resolved to its fund ISIN first. Provide this or isin.

Output Schema

Name	Required	Description	Default
`fund`	Yes
`found`	Yes
`query`	Yes
`webPage`	No
`listings`	Yes
`warnings`	Yes
`platformLink`	No

Schema Changelog

Changes observed during successful MCP inspections.

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.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint, so the bar is lower; the description still adds real context by spelling out the resolution path (ticker → fund ISIN) and the unit convention 'Ratios are percentage points.' The trailing 'Read-only' restates the annotation and earns nothing.

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 key differentiator ('Resolve one FUND rather than one listing') is front-loaded, and the remaining sentences move from inputs to outputs to use cases with little waste. The final 'Read-only' is redundant filler against the annotations.

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?

An output schema exists and the input schema is fully described, so nothing more is required; the description still previews the payload shape, which helps an agent choose this tool over the ETF snapshot/search siblings. Complete for a read-only lookup.

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 both parameters (isin, ticker) are already documented with examples in the schema. The description's 'any venue ticker of the fund' and 'or any venue ticker' framing slightly reinforces the either/or input but adds no format or constraint detail beyond the schema.

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?

States a specific verb and resource — resolve a FUND (not a listing) from an ISIN or venue ticker — and enumerates exactly what comes back: identity, costs, index, distribution policy, wrapper type, and all venue listings with exchange and currency. That distinction from listing-level siblings (get_etf_snapshot, get_etf_holdings) is made explicit in the first sentence.

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

Usage Guidelines4/5

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

Gives three concrete trigger conditions (user quotes an ISIN, asks which ticker to buy on their exchange, or several tickers may be the same fund), which is genuinely actionable routing guidance. It does not name alternative tools or state when this is the wrong choice.

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.