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

yfinance-ai MCP server

by lkcair
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_mutualfund_holders

Read-onlyIdempotent

Retrieve the mutual funds that hold a given stock by ticker symbol, helping you analyze institutional fund ownership and shareholder composition.

Instructions

Get mutual fund holders.

Args: ticker: Stock ticker symbol

Returns: List of mutual funds holding the stock

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_mutualfund_holders"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/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 the safety profile is fully covered. The description adds little beyond the return type; it omits any notes on data freshness, pagination, or external lookups implied by openWorldHint.

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?

Very short and front-loaded; the purpose leads and the args/returns sections are minimal. Slightly bloated by the docstring-style 'Args:'/'Returns:' scaffolding, but efficient overall.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values needn't be explained, and the read-only annotations cover safety. But for a tool with 0% schema coverage and multiple confusable siblings, the description leaves too much inference for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, but it only restates 'ticker: Stock ticker symbol' matching the parameter name. No format, exchange prefix, or validation guidance is added.

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 clear verb ('Get') and resource ('mutual fund holders'), and specifies it returns funds holding a stock. However, it does not distinguish itself from close siblings like get_institutional_holders, get_major_holders, or get_fund_holdings, which an agent could easily confuse.

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?

Provides no when-to-use guidance, no exclusions, and no mention of the numerous alternative holder/ownership tools in the sibling set. An agent must infer that this returns mutual-fund ownership specifically versus institutional or insider holders.

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