Skip to main content
Glama

SN Data by Shikshan Nivesh

Financial statements

get_financials
Read-onlyIdempotent

Income statement, balance sheet and cash flow by fiscal year or quarter. As reported (the default) gives each line as the company filed it, with the 10-K or 10-Q behind each period; standard gives the same named lines for every company, for comparing companies. Each period carries the filing it came from.

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
basisNoas-reported (the default, with filings) or standard lines.
linesNoOnly lines whose name contains one of these words, comma separated, like revenue,net income,cash.
periodNoFiscal years or quarters. Default annual.
tickerYesThe company's ticker, like AAPL. BRK.B and BRK-B both work.
periodsNoHow many of the latest periods. Default 5 years or 8 quarters.
statementNoWhich statement. Default all.

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 this a safe, idempotent, closed-world read, so the bar is lower. The description still adds useful behavior beyond them: it discloses provenance semantics ('the 10-K or 10-Q behind each period') and restates the default basis, which matters when an agent omits parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the resource, which is good, but the final sentence 'Each period carries the filing it came from' duplicates the earlier 'with the 10-K or 10-Q behind each period.' One of the two provenance mentions is redundant filler.

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 explaining what comes back: three statement types, periods by fiscal year or quarter, and filing provenance per period. Combined with a fully documented six-parameter schema, an agent has enough to call it correctly; only the response shape remains unstated.

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 100% and each of the six parameters already has an inline description, including the same as-reported/standard explanation. The description largely repeats that schema text, adding only the comparability rationale for 'standard'. Baseline 3 is appropriate since the schema carries the parameter burden.

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?

Names the exact resources retrieved (income statement, balance sheet, cash flow) and the two axes of scope (fiscal year vs quarter). It never says 'retrieves/returns' explicitly, but the resource and dimensions are unambiguous and clearly distinct from siblings like get_segments or get_company.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives real selection guidance for the key mode choice: 'as reported ... gives each line as the company filed it' versus 'standard gives the same named lines for every company, for comparing companies.' That tells the agent which basis to pick for a comparability use case. It does not address when to prefer this tool over siblings such as get_segments, so no exclusions are stated.

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