Skip to main content
Glama

fetch_income_statement

[Personal research only] Fetch annual and quarterly income statement data including revenue, expenses, net income, EPS, and other profit & loss metrics.

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": "fetch_income_statement"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesStock ticker symbol (e.g., 'AAPL', 'MSFT', 'GOOGL') for which to retrieve annual and quarterly inco…

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It conveys that this is a read operation scoped to annual and quarterly periods and enumerates the metric categories returned, which is useful context. It says nothing about history depth, currency, data source, rate limits, or coverage gaps in the data, which are the traits an agent would want for a market-data read tool.

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?

A single front-loaded sentence with no filler, and the listing of metrics is compact rather than verbose. The only mild drag is the bracketed disclaimer occupying the opening position, but it carries real usage meaning.

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 one-parameter read tool with no output schema, the description usefully enumerates the fields returned, which compensates for the missing output schema. It is not fully complete on period coverage limits or data recency, but nothing critical for invoking the tool is absent.

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?

Only one parameter with 100% schema description coverage, and the schema already supplies ticker examples ('AAPL', 'MSFT', 'GOOGL'). The description restates the symbol scope but adds no formatting rules, exchange suffix conventions, or case-sensitivity guidance beyond the schema, so baseline 3 applies.

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?

States a specific verb ('Fetch') plus the resource ('annual and quarterly income statement data') and names the metrics returned (revenue, expenses, net income, EPS). This clearly separates it from sibling tools like fetch_balance_sheet and fetch_cash_flow without the agent needing to open any schema.

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 '[Personal research only]' tag signals the intended usage context, and the annual/quarterly scope implies financial-statement use. However, it never states when to prefer this over siblings such as fetch_earnings or financials, nor does it give any exclusions or prerequisites.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources