Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Yahoo Finance statement periods

yahoo_finance_financials_list
Read-onlyIdempotent

Lists Yahoo Finance income, balance-sheet, and cash-flow statement periods for a ticker symbol, so you can inspect available annual, quarterly, or trailing financial data.

Instructions

List Yahoo Finance income, balance-sheet and cash-flow periods. 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_financials_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNoStatement period. Default: `annual`.
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.
statementNoStatement to return. Default: `income`.
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, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond annotations: "Returns a list" conveys no ordering, no notion of what a period actually is (fiscal labels, dates, or keys), and no pagination or rate-limit context for an open-world network call.

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 action and the resource, with no padding. The closing "Returns a list" is low-value filler given the absence of any real return description, which keeps it from a 5.

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?

There is no output schema, so the description must explain results, yet "Returns a list" does not say a list of what (period identifiers, fiscal year ends, labels). Inputs are well covered by a rich schema and annotations handle safety, so an agent can call it correctly but cannot anticipate the response shape.

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% across all six parameters, including enum descriptions for `period` and `statement`, so the schema already carries the semantic load. The description only restates the `symbol` requirement and does not add format or default hints beyond what the schema documents; 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?

"List Yahoo Finance income, balance-sheet and cash-flow periods" gives a specific verb plus resource and enumerates the three statement types covered, which separates it from siblings like yahoo_finance_fundamentals_list or yahoo_finance_transcripts_list. It stops short of explicitly naming a differentiating sibling, so it is clear but not maximally disambiguating.

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 offered is the prerequisite "Requires `symbol`". There is no statement of when to call this rather than fundamentals_list or transcripts_list, no note that this is a discovery step before fetching actual statement data, and no exclusion of cases where the endpoint would be a poor fit.

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