Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Financial statements

financial_statements
Read-onlyIdempotent

Retrieve income statements, balance sheets, and cash flow reports for a stock symbol, with quarterly, annual, or other period types selected by request parameters.

Instructions

Income statement, balance sheet or cash flow of one symbol, quarterly or annual (report_type and statement_type select which).

Values are in the currency and scale the response states (often IDR billions).

Returns (Stockbit's data field): data{currency['IDR','USD'], default_currency, rounding_value[1e9,1e6], html_report (pre-rendered HTML table; rows .acc-name with data-lang-0/1 ID/EN labels), data_tables{periods[], accounts[], max_show_level}}. Currency/rounding/language are client-side formatting only (not sent).

Paywall: unknown.

Endpoint: GET exodus /findata-view/company/financial.

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>",
      "report_type": "<report_type>",
      "statement_type": "<statement_type>"
    },
    "name": "financial_statements"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesTicker
data_typeNoOnly literal seen in bundle Default "DATA_TYPE_REPORTED".
report_typeYes1=Income Statement, 2=Balance Sheet, 3=Cash Flow Default "1".
statement_typeYes1 Quarter, 2 Annual, 3 TTM, 4 Interim YTD, 5 Q1, 6 Q2, 7 Q3, 8 Q4, 9 QoQ Growth, 10 Quarter YoY Growth, 11 YTD YoY Growth, 12 Annual YoY Growth, 13 3 Year CAGR Default "1".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already grant readOnly, idempotent, non-destructive, and openWorld, so the safety profile is covered and the description does not contradict it. The description adds genuinely non-obvious behavior: values are in a client-specified currency and scale (often IDR billions), currency/rounding/language are client-side formatting only and never sent to the server, and paywall status is unknown. Missing only pagination/rate-limit style details, which are largely irrelevant for a single-symbol lookup.

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 purpose is front-loaded in the first sentence, then response shape, formatting caveats, and endpoint follow in short labeled fragments. The Returns block is dense and includes HTML row-class trivia that is borderline over-specific, but with no output schema the return-shape detail earns most of its space.

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 compensates by describing the data envelope (currency, rounding_value, html_report, data_tables) and by flagging that currency and language formatting are client-side. It is complete enough to invoke correctly; only explicit sibling routing is absent.

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%, with report_type and statement_type already fully enumerated in the schema, so the baseline is 3. The description reiterates the division of labor between those two parameters and clarifies the scale of returned values, but adds no syntax or format detail the schema lacks.

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 the exact resource (income statement, balance sheet, cash flow for one symbol) at quarterly or annual granularity, which is immediately distinguishable from ratio, keystats, or chart siblings by resource type. It does not explicitly name or contrast any sibling, 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?

It explains that report_type and statement_type select which statement and period, which implies when the tool is appropriate, and the paywall note gives a precondition caveat. However there is no explicit when-to-use versus when-not guidance or pointer to alternatives like financial_ratios for derived metrics.

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

Deploy Server

Other Tools