Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

yahoo_finance_ticker_financials

Read-only

Fetch Yahoo Finance income statement, balance sheet, or cash flow data for a symbol. Choose annual, quarterly, or supported trailing frequency; use this to inspect reported financial statements.

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>"
    },
    "name": "yahoo_finance_ticker_financials"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNoannual, quarterly, or trailing.
symbolYesYahoo Finance symbol such as AAPL.
statementNoincome, balance-sheet, or cash-flow.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the data source (Yahoo Finance) and the available statement/period dimensions, but says nothing about data freshness, whether 'trailing' is always available, or how missing statements are handled.

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 tight sentences: the resource and source are front-loaded, then the selectable dimensions. 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?

Output schema exists, so return values need no explanation, and the three parameters are all covered. The definition is nearly complete for a simple financials fetch, with only the fine-grained body(ies) of the statement and cross-sibling routing left implicit.

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%, so the schema already documents symbol, period, and statement. The description mirrors the period and statement values and hints that trailing may not always be supported, but adds no syntax or format detail beyond the schema — baseline 3 is appropriate.

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 (Fetch) plus resource (income statement, balance sheet, cash flow) scoped to Yahoo Finance and a symbol. It is clear what the tool returns, though it does not name any sibling (e.g., sec_financials, google_finance_financials, yahoo_finance_ticker_earnings) to route the agent away from alternatives.

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?

The closing clause 'use this to inspect reported financial statements' gives an implied use case, but there is no explicit when-to-use/when-not guidance, no mention of how it relates to sibling financial endpoints, and no prerequisites for the symbol.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources