Skip to main content
Glama

FinanceQuery

Financial Statements

get_financials
Read-onlyIdempotent

Get income statement, balance sheet, or cash flow statement for one or more stock symbols (comma-separated). A single symbol returns one statement; multiple symbols return a batch plus per-symbol errors.

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": {
      "symbols": "<symbols>",
      "statement": "<statement>",
      "frequency": "<frequency>"
    },
    "name": "get_financials"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated list of GraphQL field names to include; omitted = curated default set
metricsNoComma-separated list of line-item metrics to filter to; omitted = all reported metrics
symbolsYesOne or more comma-separated ticker symbols (e.g., "AAPL" or "AAPL,MSFT,GOOGL")
frequencyYesReporting frequency: annual | quarterly (default: annual)
statementYesStatement type: income | balance | cashflow

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description still adds genuinely new behavior: batch mode with per-symbol errors when multiple symbols are supplied, which tells the agent to expect partial results rather than an all-or-nothing failure.

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, front-loaded with the core capability, and the batch/error caveat follows immediately with 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 five-parameter read-only retrieval tool with no output schema, the description covers purpose, statement variety, and batch semantics adequately. It does not describe the shape of a returned statement or how fields/metrics interact with the default curated set, leaving minor gaps filled by the schema.

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 all five parameters including fields and metrics are already documented in the schema. The description adds little beyond that except the single-vs-multiple symbol return behavior; the statement values it lists merely restate the schema.

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 verb ('Get') and concrete resources ('income statement, balance sheet, or cash flow statement') scoped to stock symbols, so an agent knows exactly what it retrieves. It does not name or differentiate from nearby siblings such as get_edgar_facts or get_key_metrics_ttm, which keeps it short of a 5.

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?

Usage is implied rather than stated: the agent can infer it should call this when it needs a full financial statement for tickers. There is no explicit when-not guidance, no mention of alternatives for fundamental data, and no prerequisites for the statement/frequency choice.

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.