Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Yahoo Finance symbols

yahoo_finance_lookup
Read-onlyIdempotent

Search Yahoo Finance for stock, ETF, index, fund, futures, currency, and crypto symbols by text and instrument type; return paginated results with a cursor.

Instructions

Search Yahoo Finance symbols by text and instrument kind. Requires query. Returns a list (use cursor when paginated).

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

Input Schema

NameRequiredDescriptionDefault
typeNoInstrument kind. Default: every kind.
limitNoPage size as an integer from 1 to 250. Default: 25.
queryYesRequired. Text to search for, e.g. `apple`, `toyota` or `AAPL`.
cursorNoCursor from `page.nextCursor` of the previous response. It only works with the same filters.
offsetNoZero-based position to begin the list at. Default: 0; maximum: 1,000,000. Only the first 10,000 rows are available; past that the page is empty.
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, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is fully covered structurally. The description adds only a brief note that results are a list and that the cursor should be used when paginated, which is thin extra context for an open-world search tool.

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 with the core purpose front-loaded and no padding. The "Requires `query`" clause is mildly redundant with the schema's required list, but the description is not bloated.

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 eight parameters, three required, and no output schema, the description does the minimum: it names the resource and hints at list pagination. It omits result shape, ordering behavior, and any differentiation from sibling search tools, which matters given a large catalog of adjacent Yahoo Finance tools.

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 type, limit, cursor, offset, context, llm_model and conversation_id is already documented in the schema. The description only restates that query is required and that cursor applies to pagination, adding essentially no meaning beyond the structured fields.

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 (search) and resource (Yahoo Finance symbols) plus the filtering dimension (text and instrument kind), which is clearer than the title alone. However, it never distinguishes itself from the closely named siblings yahoo_finance_search and yahoo_finance_screener_search, so an agent cannot tell from the description which search entry point to pick.

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 `query`" is a prerequisite, not usage guidance, and the schema already marks query as required. There is no statement of when to use this symbol-lookup over yahoo_finance_search or yahoo_finance_screener_search, and no exclusions or typical scenarios are given.

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