Skip to main content
Glama
screener-mcp
by LogeshR15

get_financials

Read-only

Retrieve an Indian company's financial statements—profit and loss, balance sheet, cash flow, or ratios—by NSE/BSE symbol, with consolidated/standalone data and up to 12 fiscal years.

Instructions

Get financial statements for a company, as numbers (₹ Cr unless the label says % or days).

symbol: NSE/BSE symbol statement options: "profit_loss" — Revenue, expenses, operating profit, PAT (default). The trailing-twelve-months column comes back as data.ttm, separate from the fiscal years. "balance_sheet" — Assets, liabilities, equity, debt "cash_flow" — Operating, investing, financing cash flows "ratios" — Screener's ratios table (debtor/inventory/payable days, cash conversion cycle, working-capital days, ROCE) plus ROE %, debt-to-equity, and year-end P/E and P/B. data.row_sources says where each row comes from. financial_type: "consolidated" or "standalone" years: number of fiscal years (default 5, max 12) — TTM is never counted

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

Input Schema

NameRequiredDescriptionDefault
yearsNo
symbolYes
statementNoprofit_loss
financial_typeNoconsolidated

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, openWorldHint=true), and the description layers on real behavioral detail: TTM is returned separately at data.ttm, TTM is never counted against the years limit, and data.row_sources explains provenance in the ratios table. It stops short of noting failure modes (invalid symbol, missing statement type) or data latency.

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?

Front-loads the core purpose and units in one line, then organizes the rest as a compact per-parameter breakdown. The per-statement glosses each add decision-relevant content, though the ratios entry is longer than strictly necessary.

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

Completeness5/5

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

An output schema exists, so return values needn't be explained, yet the description still flags the two non-obvious response shapes (data.ttm and data.row_sources). All four parameters are covered, so an agent has everything needed to call this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and does: symbol is an NSE/BSE symbol, statement's four allowed values are enumerated with their contents despite no enum in the schema, financial_type's consolidated/standalone options are named, and years gets a default (5) plus a max (12) and TTM exclusion rule.

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+resource ('Get financial statements for a company') and adds unit semantics (₹ Cr unless the label says % or days). The enumerated statement options make clear what content categories are retrievable, though it never names a sibling (e.g. get_quarterly_results) to draw the boundary explicitly.

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 context is implied through the statement menu — an agent can infer 'use ratios for debtor/inventory days, cash_flow for cash flows' — and defaults are given (profit_loss, consolidated, 5 years, max 12). There is no explicit when-to-use/when-not guidance and no named alternative for overlapping needs like quarterly or peer data.

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