Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Yahoo Finance fundamental metrics

yahoo_finance_fundamentals_list
Read-onlyIdempotent

Retrieve Yahoo Finance fundamental metric values for a stock symbol and selected period to compare financials such as revenue, net income, or free cash flow.

Instructions

List Yahoo Finance fundamental metric values for a symbol and period. Requires symbol and metrics. 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>",
      "metrics": "<metrics>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "yahoo_finance_fundamentals_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.
metricsYesRequired. Metric names such as `TotalRevenue`, `NetIncome` or `FreeCashFlow`, 1 to 100, comma-separated. Unknown names are refused.
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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds only 'Returns a list', with no detail on item shape, result ordering, error behavior for unknown metrics, or how trailing versus annual data differ — near-zero value beyond structured fields.

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 with the verb and resource front-loaded and no filler. The middle sentence restates the required fields already declared by the schema, which is the only wasted line.

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?

Parameters are fully covered by the schema, but there is no output schema and 'Returns a list' does not tell an agent what a metric record contains or how multiple metrics are ordered. For a 6-parameter tool returning arbitrary metric values, that is the one material gap.

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%, with symbol patterns, metric name examples, period default and the 1-100 bound all documented in the schema. The description only echoes the two required parameters and adds no meaning beyond it, so the baseline of 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?

Names a specific verb (List) and resource (Yahoo Finance fundamental metric values) scoped to a symbol and period. It is clear on its own, but it never distinguishes itself from close siblings such as yahoo_finance_financials_list or yahoo_finance_statistics_get, so an agent cannot tell from the text which one returns 'fundamental metrics' versus statements or summary statistics.

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 the prerequisite 'Requires `symbol` and `metrics`', which merely restates the required schema fields. There is no when-to-use framing, no mention of when to prefer the financials or statistics siblings, and no note about metric-name validation being a precondition for success.

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