Skip to main content
Glama

FinanceQuery

ETF Profile and Holdings

get_etf_profile
Read-onlyIdempotent

Get an ETF's profile and holdings (net assets, expense ratio, sector/country weightings, top holdings).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "get_etf_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated list of GraphQL field names to include; omitted = all fields
symbolYesETF ticker symbol

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds the data categories returned, which is useful, but says nothing about data freshness, ETF universe coverage, or pagination/size limits on the holdings list.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the resource named first and the returned data summarized in a compact parenthetical. Every clause earns its place; nothing is redundant.

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 two-parameter read tool with no output schema, the description does enough by enumerating the main return categories. Minor gap: no indication of how the nested holdings and weighting sections are shaped or how large they get.

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 are documented in the schema, giving a baseline of 3. The description never references the 'fields' projection parameter or the required 'symbol', so it adds no meaning beyond the schema.

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?

States a specific verb ('Get') and resource ('an ETF's profile and holdings') and enumerates the contents (net assets, expense ratio, sector/country weightings, top holdings). The ETF scoping separates it from get_company_profile, though no sibling is named explicitly.

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 the ETF-specific framing — call it when you need an ETF's fundamentals or holdings. There is no statement of when to prefer get_holders or get_company_profile instead, and no prerequisites or exclusions are given.

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.