Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Yahoo Finance fund profile

yahoo_finance_fund_get
Read-onlyIdempotent

Retrieve a fund's Yahoo Finance profile, performance data, and top holdings using its ticker symbol to evaluate the fund.

Instructions

Get Yahoo Finance fund profile, performance and top holdings. 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_fund_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

B3.2/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 covered. The description adds a lightweight return-scope hint ('profile, performance and top holdings') which is useful given there is no output schema, but it says nothing about data availability (e.g., fund-only symbols), coverage, or failure behavior.

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 payload, with zero filler. It is efficient but so terse that the second sentence is largely redundant with the required-fields list in the schema.

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?

With no output schema, the description must at least sketch the return shape, and 'profile, performance and top holdings' does so minimally. For a tool with four parameters and a large sibling family, it leaves the agent without enough to judge fit versus adjacent Yahoo Finance getters.

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%, and all four parameters including the camel-case ticker format and the meta-parameters are documented in the schema itself. The description only echoes 'Requires `symbol`' and adds no syntax, format, or usage nuance 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 fund profile, performance and top holdings'), so an agent knows the payload shape. It does not distinguish itself from near-siblings such as yahoo_finance_profile_get or yahoo_finance_holders_get, so scope ('fund' vs. equity profile) must be inferred.

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 guidance is 'Requires `symbol`', which restates the schema's required field rather than telling the agent when to call this instead of profile_get or holders_get. There are no exclusions, no preconditions, and no alternative routing.

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