Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List related Yahoo Finance tickers

yahoo_finance_related_list
Read-onlyIdempotent

Retrieve related Yahoo Finance tickers and recommended symbols for a given ticker to support peer analysis and market research.

Instructions

List related Yahoo Finance tickers and recommended symbols. Requires symbol. Returns a list.

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

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 readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered without the description. The description adds only 'Returns a list', which is nearly tautological for a *_list tool and says nothing about what 'related' means (same sector peers? other listings? Yahoo recommendations?), freshness, or result size.

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?

Three short sentences, front-loaded with the purpose, with no filler or hedging. The only low-value line is 'Returns a list', which conveys almost nothing given the tool name and annotations.

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?

The tool is a simple read-only list with fully documented parameters and no output schema, so the description is adequate to invoke it correctly. It falls short on explaining what the returned 'related' tickers actually represent, which is the one piece of information an agent cannot get from the schema or annotations.

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 the context/llm_model/conversation_id handshake are already documented in the schema; the baseline of 3 applies. The description's only parameter mention ('Requires `symbol`') repeats the schema without adding syntax or semantics, though it usefully flags the one parameter that determines the result.

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 ('List related Yahoo Finance tickers and recommended symbols'), which is enough to tell an agent this is a recommendation/discovery tool rather than a data-retrieval tool like quotes_list or chart_get. It does not name or contrast with any sibling, so the differentiation is inferred rather than stated.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative. 'Requires `symbol`' restates the schema's required field rather than explaining the condition under which an agent should pick this tool over yahoo_finance_lookup, yahoo_finance_search, or yahoo_finance_instrument_get.

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