Skip to main content
Glama

FinBridge

Screen ETFs (FinBridge DB)

screen_etfs
Read-only

Screen exchange-traded funds in the local finbridge database on the things that actually distinguish an ETF: premium/discount to NAV, fund size (AUM), the index it tracks, price momentum, and — for US funds — the audited calendar-year TOTAL return from the fund's own prospectus.

Funds only. For an operating company use get_valuation (one company) or query_db (many at once).

⚠Funds file no annual financial statements, so the statement-based tools (get_dart_financials, get_valuation) have nothing to say about them — that is why they are screened here instead.

Coverage differs by market and the response says so per row:

  • KR (1,170 listed ETFs): NAV, AUM (net assets, KRW), listed units and the tracked index come from the same daily feed as prices, 2020-01-02 onward. premium_pct is close/NAV-1 computed on the SAME day (mixing dates would be meaningless).

  • US (5,868 ETFs): no NAV or AUM source exists that we may redistribute, so those fields are null. Instead total_return_pct carries the fund's audited calendar-year total return (distributions reinvested) from SEC prospectus data — the only distribution-inclusive number available.

⚠ret_20d / ret_120d are PRICE returns in every market: ETF distributions are not in the daily bars, so income funds look worse than they were. For US funds compare against total_return_pct to see the gap. ⚠aum is in the listing currency (KRW today). Do not rank across markets on it. ⚠total_return_pct is pinned to ONE calendar year across all rows (reported as total_return_year), because prospectus refresh dates differ per fund — ranking a 2024 figure against a 2025 one would be a silently wrong table.

Args:

  • market: 'kr', 'us', or 'all' (default)

  • min_aum: minimum net assets in listing currency (KR only; e.g. 100000000000 = 1,000억)

  • max_abs_premium_pct: keep funds trading within this |premium| of NAV, e.g. 0.5

  • min_premium_pct: keep funds at or above this premium (negative values find discounts)

  • min_price, min_volume: liquidity floors (vol_avg20 is the 20-session average)

  • index_contains: substring of the tracked index name — 'TR' finds total-return index trackers, '코스피' finds KOSPI trackers

  • name_contains: substring of the fund name or ticker

  • total_return_year: calendar year for total_return_pct; omit for the best-covered year

  • sort_by: aum | premium | abs_premium | ret_20d | ret_120d | ret_250d | volume | total_return (default aum); order: 'asc'|'desc' (default desc)

  • limit: 1-100 (default 20); response_format: 'markdown'|'json'

Returns: {count, market, total_return_year, sort_by, order, rows: [{market, symbol, name, as_of, close, nav, premium_pct, aum, index_name, ret_20d, ret_120d, vol_avg20, total_return_pct, total_return_period}]}

Examples:

  • Large KR ETFs trading close to fair value: {market:'kr', min_aum: 100000000000, max_abs_premium_pct: 0.3, sort_by:'aum'}

  • KR ETFs at the deepest discount to NAV: {market:'kr', sort_by:'premium', order:'asc'}

  • KR trackers of a total-return index: {market:'kr', index_contains:'TR', sort_by:'aum'}

  • US ETFs by audited total return: {market:'us', sort_by:'total_return'}

Use when: choosing or comparing funds. Don't use for stocks (get_valuation / query_db) or for a single fund's price history (get_stock_prices). Errors: 'database has not been built yet' — ingest has not run; an empty result is not an error (count 0).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "screen_etfs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows, 1-100 (default 20)
orderNoSort direction (default desc)desc
marketNoMarket: 'kr', 'us', or 'all' (default)all
min_aumNoMinimum net assets in listing currency (KR only; US is null)
sort_byNoSort key (default aum)aum
min_priceNoMinimum last close in listing currency
min_volumeNoMinimum 20-session average volume
name_containsNoSubstring of the fund name or ticker
index_containsNoSubstring of the tracked index name ('TR' for total-return indices)
min_premium_pctNoKeep funds at or above this premium in percent (negative finds discounts)
response_formatNo'markdown' for a table, 'json' for compact outputmarkdown
total_return_yearNoCalendar year for total_return_pct; omit for the best-covered year (the response says which)
max_abs_premium_pctNoKeep funds within this |premium to NAV| in percent

Output Schema

NameRequiredDescriptionDefault
rowsYes
countYes
orderNo
marketYes
sort_byNo
data_as_ofNo
total_return_yearNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / properties / data_as_of / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "properties": {},
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {},
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / order / $ref
      Removed value: -"#/properties/sort_by"
    • addedOutput schema / properties / order / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / rows / items / additionalProperties
      Previous value: -trueNew value: +{}
  2. Added
  3. Removed
  4. Changed1 schema field changed
    • addedOutput schema / properties / data_as_of
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "properties": {},
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
  5. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say readOnly/closed-world; the description goes far beyond by disclosing per-market data coverage (KR NAV/AUM from 2020, US NAV/AUM null), the currency of AUM and the warning not to rank across markets, that ret_20d/ret_120d are price-only returns excluding distributions, and that total_return_pct is pinned to a single calendar year. It also states the error string and that an empty result (count 0) is not an error.

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?

Front-loaded purpose, then warnings, then args, examples, use-when and errors in a predictable order. It is longer than strictly necessary — the coverage bullets repeat some parameter semantics — but nearly every sentence carries decision-relevant information.

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 13-parameter screening tool with an output schema, the description covers scope, per-market caveats, argument recipes, sorting defaults, error behavior and the return row shape. Nothing an agent needs in order to call it correctly or interpret results is missing.

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 already 100%, so the baseline is 3; the description adds practical meaning on top — min_aum is KR-only with a 1,000억 worked value, index_contains 'TR' means total-return trackers, and total_return_year omitted yields the best-covered year. A few of these echo schema text, so it falls short of fully additive.

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 concrete verb and resource ('Screen exchange-traded funds in the local finbridge database') and immediately names the attributes being screened on. It also explicitly carves out non-ETF scope by pointing to get_valuation and query_db, so an agent can distinguish it from every sibling without opening a 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?

Includes an explicit 'Use when: choosing or comparing funds' plus 'Don't use for stocks (get_valuation / query_db) or for a single fund's price history (get_stock_prices)', naming both alternatives and the exclusion conditions. Worked examples map common intents to argument sets.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.