Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Yahoo Finance holders

yahoo_finance_holders_get
Read-onlyIdempotent

Fetch Yahoo Finance institutional and fund holders plus a holder breakdown for a ticker symbol to analyze ownership structure and concentration.

Instructions

Get Yahoo Finance institutional and fund holders and holder breakdown. Requires symbol.

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "yahoo_finance_holders_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesRequired. Ticker symbol, case-insensitive, e.g. `AAPL`, `^GSPC`, `EURUSD=X`, `BTC-USD`, `7203.T`.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world access, so the safety profile is covered structurally. The description adds nothing beyond that — no note on data freshness, whether quarterly filings drive the holder data, or what the breakdown covers — so it does not earn credit for extra behavioral context.

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?

Two short sentences, front-loaded with the resource and scope. The second sentence is redundant with the schema's required field, so it is efficient but not maximally economical.

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?

For a simple read-only lookup with full schema coverage and annotations, the description is mostly sufficient. It leaves open what 'holder breakdown' contains — major holders, institutional percentage, or fund positions — which matters for an agent deciding whether this tool answers the user's question.

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 all four parameters, including symbol format examples and the context/llm_model/conversation_id conventions, are fully documented in the schema. The description's 'Requires `symbol`' merely repeats that, adding no new semantics 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 and resource: 'Get Yahoo Finance institutional and fund holders and holder breakdown,' which tells an agent this returns ownership data, not price or profile data. It does not explicitly name differentiating siblings such as insiders_get or fund_get, so it is clear but not fully disambiguating.

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 only usage statement is 'Requires `symbol`,' which is already enforced by the schema's required list. There is no guidance on when to reach for holder data versus insiders, fund, or profile endpoints, and no exclusions or prerequisites.

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