Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Yahoo Finance

yahoo_finance_search
Read-onlyIdempotent

Search Yahoo Finance entities, news, lists, and research reports by query to retrieve relevant market and company information.

Instructions

Search Yahoo Finance entities, news, lists and research reports. Requires query. 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": {
      "query": "<query>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "yahoo_finance_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesRequired. Text to search for, e.g. `apple`, `toyota` or `AAPL`.
regionNoMarket region, a two-letter code such as `US`, `GB` or `JP`.
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, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description's one addition of substance is "Returns a list," which is genuinely helpful given there is no output schema, but it says nothing about result limits, ordering, or the multi-call conversation_id handshake implied by the schema.

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 and free of padding. It is efficient, though the terseness leans toward under-specification rather than deliberate conciseness.

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 six-parameter, three-required tool with no output schema, the description covers the required argument and the return shape but omits any routing guidance among its many siblings. The heavy documentation in the schema compensates for most parameter-level gaps, leaving the missing differentiation as the main shortfall.

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 every parameter including region, language, context, llm_model and conversation_id is already documented in the input schema. The description only repeats that `query` is required, adding no meaning beyond the structured fields; baseline 3 applies.

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?

The description gives a concrete verb ("Search") and enumerates the resource scope ("Yahoo Finance entities, news, lists and research reports"), so an agent knows broadly what it retrieves. It does not, however, distinguish the tool from siblings such as yahoo_finance_lookup or yahoo_finance_news_list, which cover overlapping territory.

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 `query`," which merely restates a schema constraint. There is no guidance on when to prefer this generic search over the many specific siblings (news_list, lookup, instrument_get) or when not to use it.

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