Skip to main content
Glama
Sign In
yfinance-ai MCP server

yfinance-ai MCP server

by lkcair
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_fund_overview

Read-onlyIdempotent

Retrieve key overview metrics for an ETF or mutual fund by ticker, including category, family, total assets, and expense ratio.

Instructions

Get overview data for an ETF or mutual fund.

Args: ticker: Fund ticker symbol (e.g., 'VOO', 'SPY', 'QQQ', 'ARKK')

Returns: Fund category, family, total assets, expense ratio, and other key metrics

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": {
      "ticker": "<ticker>"
    },
    "name": "get_fund_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The description adds only what data comes back, and since an output schema exists that listing is largely redundant; no auth, rate-limit, or coverage caveats are mentioned.

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?

Short, front-loaded, and structured with Args/Returns sections so the key information appears first. The Returns block slightly duplicates the output schema, which is the only real waste.

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 single-parameter read tool with full annotations and an output schema, the description covers purpose, input format, and return shape. The remaining gap is competitive positioning against sibling fund tools, which is a usage-guidance concern rather than missing invocation-critical detail.

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 description coverage is 0%, so the description does the work for the single parameter by naming it and giving concrete examples ('VOO', 'SPY', 'QQQ', 'ARKK'). That confirms the expected symbol format, though it omits any note about invalid or ambiguous tickers.

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 and resource: "Get overview data for an ETF or mutual fund." This clearly separates it from equity-focused siblings like get_company_overview, though it never explicitly names the fund-specific alternatives (get_fund_holdings, get_fund_sector_weights) that could be confused with it.

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

Usage Guidelines2/5

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

The description offers no when-to-use guidance, no prerequisites, and no routing to alternatives. With siblings such as get_fund_holdings and get_fund_sector_weights available, an agent gets no help deciding which fund tool answers its question.

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

Deploy Server

Other Tools