Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Yahoo Finance earnings

yahoo_finance_earnings_get
Read-onlyIdempotent

Retrieve quarterly and yearly earnings, estimates, and history for a Yahoo Finance ticker symbol to analyze company performance.

Instructions

Get Yahoo Finance quarterly and yearly earnings, estimates and history. Requires symbol.

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

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

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered without the description's help. The description adds the content scope (quarterly and yearly earnings, estimates, history), which is mild value, but says nothing about upstream data availability, symbol validity failures, or rate behavior on an open-world remote source.

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, front-loaded with the substantive content scope. The trailing "Requires `symbol`" is redundant with the schema's required list but costs little and does not obscure the main statement.

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 no output schema, the description carries some burden for describing the return, and it does list the content types returned. However, it does not indicate the shape of the response (time series vs. nested period objects), whether estimates are forward-looking, or how history depth is bounded, which matters for an earnings data tool.

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% and all four parameters, including the unusual context/llm_model/conversation_id handshake, are documented in the schema itself. The description only echoes the symbol requirement, adding no new meaning; the baseline 3 applies when the schema does the heavy lifting.

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?

"Get Yahoo Finance quarterly and yearly earnings, estimates and history" names a specific verb and resource and scopes the data returned (quarterly vs. yearly, estimates and historicals). It does not explicitly distinguish itself from nearby siblings such as yahoo_finance_financials_list or yahoo_finance_transcript_get, but the resource is unambiguous from the name and sentence.

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 is "Requires `symbol`," which restates a schema requirement rather than a usage condition. There is no statement of when to pick this over financials_list, transcript_get, or calendar_list, and no note about which symbol universe is valid across the many sibling tools.

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