Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Yahoo Finance headlines

yahoo_finance_news_list
Read-onlyIdempotent

Fetch Yahoo Finance news headlines for a stock or index symbol with publisher links to monitor related market developments.

Instructions

List Yahoo Finance news headlines for a symbol with publisher links. 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_news_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoMarket region, a two-letter code such as `US`, `GB` or `JP`.
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.
languageNoLanguage tag for names and news, e.g. `en-US` or `ja-JP`.
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 fully covered by structured data. The description adds only that results include publisher links and come back as a list — modest value beyond annotations, with nothing on result volume, recency, or ordering.

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, front-loaded sentences with no filler. The trailing 'Returns a list' is near-tautological and is the only sentence that fails to earn its place.

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 list tool with 100% schema coverage and no output schema, the description is adequate. It is silent, however, on the three required non-obvious parameters (context, llm_model, conversation_id) and on what the returned list contains, leaving the agent to rely entirely on schema text.

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 the baseline is 3. The description restates the `symbol` requirement already documented in the schema and says nothing about region, language, or the mandatory context/llm_model/conversation_id fields, adding no meaning 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 ('List Yahoo Finance news headlines') plus the scope ('for a symbol') and a return characteristic ('with publisher links'). The 'Yahoo Finance' qualifier implicitly separates it from google_news_headlines_list, but no sibling is named, so an agent must infer the distinction from the name alone.

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?

'Requires `symbol`' is a parameter precondition, not usage guidance. The description never says when to pick this over google_news_headlines_list or yahoo_finance_trending_list, nor does it state any exclusions or context of use.

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