Skip to main content
Glama

get_financials

Read-onlyIdempotent

Fetch listed companies' quarterly and annual financials—revenue, profit, margins, debt, and growth—for Borsa Istanbul, US, and European shares, including TMS 29 inflation adjustments.

Instructions

A listed company's financial statements, for Borsa Istanbul shares (e.g. BIMAS.IS, KCHOL.IS) as for US and European ones. Use it for "how were the latest quarter's results", "what was the net profit", "did sales grow", "is it making a loss", "how indebted is it". It returns latest-quarter revenue, gross, operating and net profit with margins and debt-to-equity; quarter-on-quarter, year-on-year and annual growth, each both as reported and in constant purchasing power (real); up to eight quarters and four years of figures. Handles Turkish inflation accounting (TMS 29) and flags missing quarters, quarters that do not reconcile with the annual figure, and implausible jumps. US companies come from their official SEC filings (when configured); pass an LEI (from find_official_filer) for a European or UK company's official annual IFRS figures; other symbols use an unofficial source, so verify material figures in the company's own filings (KAP for Borsa Istanbul). Ratios are fractions.

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
symbolYesA symbol returned by search_assets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover safety and idempotency, but the description adds substantial context: data provenance (SEC filings, official IFRS via LEI, unofficial fallback for other symbols), a verification caveat pointing to KAP, TMS 29 inflation handling, the real vs reported growth split, and self-diagnostic flags for missing/non-reconciling quarters. This is well beyond what the annotations disclose.

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?

Dense and front-loaded: the purpose leads, then usage examples, then return contents and caveats. Every clause carries information, though the single long paragraph packs many concerns together and could be segmented more cleanly.

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?

No output schema exists, yet the description fully describes the returned fields (revenue, gross/operating/net profit, margins, debt-to-equity, QoQ/YoY/annual growth, history depth) and the reliability caveats. Nothing an agent needs to call and interpret it correctly is missing.

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?

With one parameter at 100% schema coverage the baseline is 3, but the description adds that the symbol may be an LEI from find_official_filer for European/UK official figures, which is meaning the schema does not state. That extra semantic detail raises it above baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence states a specific resource (a listed company's financial statements) and scope (Borsa Istanbul, US, European shares), which immediately distinguishes it from siblings like get_price_summary or get_valuation. An agent can tell what it returns without opening the schema.

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?

It supplies concrete user intents ('how were the latest quarter's results', 'what was the net profit', 'did sales grow'), which is strong when-to-use guidance, and it names find_official_filer as the source of an LEI for European/UK filers. It stops short of explicit when-not-to-use routing against siblings such as get_valuation, so it is not a full 5.

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