Skip to main content
Glama

AINDEX

A stock's financial statements

get_financials
Read-only

A US stock's income statement, balance sheet, cash flow and ratios, annual and quarterly (the last four periods each, in dollars), with the trailing year's revenue, net income, margin and free cash flow. From Nasdaq.

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": {
      "ticker": "<ticker>"
    },
    "name": "get_financials"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description usefully adds that values are in dollars, that only the last four periods are returned per cadence, and that the source is Nasdaq, but it says nothing about failure behavior for an unknown ticker, caching or latency, or how stale the data may be.

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?

A single dense sentence that front-loads the primary content (the statements) and then the supplementary trailing-year metrics, with no filler or repetition.

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?

With no output schema, the description does the work of describing return contents, cadence and units, which is close to sufficient for a one-parameter read tool. It leaves the response shape (nested by statement type?) and the identity of the ratio set unspecified.

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 coverage is 0% for the single ticker parameter, so the description would need to compensate; it only implies that the ticker refers to a US-listed stock, without restating format, case or exchange constraints. That is partial compensation for a low-coverage schema, keeping it at the baseline.

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?

The description names a specific resource, a US stock's income statement, balance sheet, cash flow, ratios, plus trailing-year revenue, net income, margin and free cash flow, so an agent knows exactly what data comes back. It does not, however, distinguish itself from nearby siblings such as get_earnings, earnings_release or analyst_estimates, which also touch company fundamentals.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative, so nothing tells the agent to pick this over get_earnings for earnings data or analyst_estimates for forecasts. Usage can only be inferred from the data list.

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