Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_finance_ticker_financials

Fetch annual, quarterly, or trailing income, balance sheet, and cash flow statements for a Yahoo Finance ticker to support financial analysis.

Instructions

Yahoo Finance financial statements. Returns annual, quarterly, or supported trailing income, balance sheet, or cash flow statement data.

Input Schema

TableJSON 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

B3.2/5.0
Behavior2/5

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

No annotations provided, and the description only states the data types returned. It doesn't disclose limitations (e.g., trailing support), authentication requirements, or response format, which is a gap for a data retrieval tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no wasted words, front-loaded with the core function. Clear and succinct.

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

Completeness2/5

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

With no output schema, the agent lacks information about the response structure and default behavior when period/statement are omitted. The description doesn't specify defaults or result format, making it incomplete for confident invocation.

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 covers all parameters with descriptions including aliases. The description adds no additional semantic value beyond restating the periods and statement types already in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it returns Yahoo Finance financial statements (income, balance sheet, cash flow) for a ticker, with period options. It distinguishes from sibling yahoo_finance_ticker_* tools which cover quotes, valuation, etc.

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?

No guidance on when to use this tool vs alternatives. It doesn't mention any conditions or exclusions, leaving the agent to infer.

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