Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_finance_ticker_financials

Fetch financial statements for a Yahoo Finance symbol. Choose income, balance sheet, or cash flow, and annual, quarterly, or trailing periods.

Instructions

Yahoo Finance financial statements. Returns financial statement data for a Yahoo Finance symbol. statement picks income, balance-sheet or cash-flow (aliases income-statement, balance and cashflow also work) and period picks annual, quarterly or trailing; trailing is supported for income and cash flow only. The response echoes statement and period, with the data under modules.

Input Schema

NameRequiredDescriptionDefault
periodNoannual, quarterly, or trailing
symbolYesYahoo Finance symbol such as AAPL
statementNoStatement type. Allowed values: income (alias income-statement), balance-sheet (alias balance), cash-flow (alias cashflow)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / period / enum
      Added value: +[
+  "annual",
+  "quarterly",
+  "trailing"
+]
    • addedInput schema / properties / statement / enum
      Added value: +[
+  "income",
+  "income-statement",
+  "balance-sheet",
+  "balance",
+  "cash-flow",
+  "cashflow"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / statement / description
      Previous value: -"income, balance-sheet, or cash-flow"New value: +"Statement type. Allowed values: income (alias income-statement), balance-sheet (alias balance), cash-flow (alias cashflow)"
  3. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the response shape (echoes statement and period, data under modules), which is genuinely helpful, but it says nothing about permissions, error behavior, or data recency covering the rest of the behavioral surface.

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?

Front-loaded with the core purpose, then parameters, then response shape. Dense but every clause earns its place; no filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter read tool with no output schema and no annotations, the description covers the parameters, a key constraint, and the return structure well enough to call it correctly. Missing only auth/error context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real value beyond the schema by stating that trailing is only valid for income and cash flow and by reaffirming the alias mappings. That constraint is not present in the schema's terse parameter descriptions.

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+resource: returns financial statement data for a Yahoo Finance symbol, and enumerates the three statement types. This clearly separates it from sibling tools like yahoo_finance_ticker_earnings or yahoo_finance_ticker_info, though it never explicitly names which sibling to prefer.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance relative to alternatives. The note that trailing period is supported only for income and cash flow is a useful conditional hint, but overall usage must be inferred from the parameter behavior.

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