Skip to main content
Glama
tearsheet

tearsheet

by kewonit

get_financials

Read-only

Retrieve a company's financial statements, including income, balance sheet, cash flow, ratios and fund flow, for Indian listed companies across up to 12 periods for direct comparison and analysis.

Instructions

Get a company's financial statement.

    Covers income statements, balance sheets, cash flow, quarterly results,
    ratios, and fund flow, which shows where money came from and went over
    trailing windows of 1 to 10 years. Accepts an NSE symbol, BSE code or
    name. Every row states its own unit, because statements mix crore,
    percent, days and multiples. A unit of as_reported means the unit isn't
    known, so don't assume one. A period starting TTM is trailing twelve
    months, and one starting Interim covers an unstated period, so don't
    compare either directly with annual columns. A blank value means no
    reliable figure exists. If the requested basis doesn't exist, the other
    is returned with a warning. Set detail to full for line items. Quarterly
    figures are checked against any matching filing in the filings folder,
    and the verification field says how that went. Other statements are
    Tijori's figures, unchecked.
    

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

Input Schema

NameRequiredDescriptionDefault
basisNoconsolidated
detailNoconcise
companyYes
periodsNo
statementNoincome

Output Schema

NameRequiredDescriptionDefault
dataYes
as_ofNo
unitsNo
entityNo
sourcesNo
warningsNo
next_cursorNo
retrieved_atNo
verificationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, and the description goes well beyond that: per-row units because crore/percent/days/multiples are mixed, `as_reported` meaning an unknown unit, TTM and Interim period semantics with a warning not to compare them to annual columns, blank values meaning no reliable figure, and basis fallback returning the other basis with a warning. It also discloses provenance asymmetry — quarterly figures are verified against matching filings via a `verification` field, while other statements are Tijori's unchecked figures.

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?

The scope statement is front-loaded and nearly every sentence carries distinct, non-redundant information about units, caveats, or provenance. Some sentences are dense and clause-stacked, notably the TTM/Interim sentence, but nothing is filler.

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?

With an output schema present, return-value documentation is unnecessary, and the description covers the interpretive hazards an agent actually needs: mixed units, unknown-unit and blank-value markers, non-comparable period prefixes, basis fallback, and verification provenance. That is sufficient for a read-only tool of this complexity.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must carry the parameter burden and largely does: `company` accepts an NSE symbol, BSE code or name; `detail=full` yields line items; `basis` explains the fallback behavior when the requested basis doesn't exist; and the statement list matches the enum values. The one blemish is the periods range — the description says 'trailing windows of 1 to 10 years' while the schema allows up to 12 — which could mislead on the upper bound.

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 opening sentence names a specific verb and resource ('Get a company's financial statement') and the follow-up enumerates the six statement types covered, which maps one-to-one onto the `statement` enum. It stops short of naming which sibling tool handles adjacent data (get_operating_metrics, get_business_mix), so the boundary is inferable rather than stated.

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 rather than prescribed: an agent learns it should set `detail` to full for line items, and that a missing basis falls back to the other with a warning. There is no explicit when-to-use-this-vs-alternatives routing, e.g. versus get_operating_metrics or company_snapshot, so selection between siblings is left to inference.

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