Skip to main content
Glama
Sign In
daniel3303

Equibles

by daniel3303
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Financial Statements

GetFinancialStatement
Read-only

Retrieve a company's income statement, balance sheet, or cash-flow statement for a specific fiscal year and period from SEC XBRL data or non-US regulatory filings, returning standard line items with restated values.

Instructions

Get a company's income statement, balance sheet, or cash-flow statement for a given fiscal year and period, sourced from SEC Company Facts (structured XBRL), or from the issuer's regulatory filings for a listing outside the US. Returns the standard line items (e.g. revenue, net income, total assets, operating cash flow) with the latest-restated value for one exact statement period end. Quarterly flow rows are always discrete quarters: when the filer reports only cumulative year-to-date values in a currency, the quarter is derived by exact subtraction from the preceding cumulative period and marked Derived. Company-specific dimensional facts (e.g. product-segment revenue) are not included — use GetRevenueBreakdown for segment/geographic revenue, and GetFinancialFact or CompareFinancialFact for one line item across periods or across companies.

Input Schema

NameRequiredDescriptionDefault
yearNoFiscal year, e.g. 2023. Defaults to the year of the latest period with line items to show.
periodNoFiscal period: 'FY' (annual) or 'Q1'..'Q4'. Defaults to the latest period with line items to show. Most filers report no discrete Q4 income/cash-flow facts in XBRL (the fourth quarter is embedded in the full-year figure) — use 'FY' for annual figures.
tickerYesStock ticker symbol (e.g., AAPL, MSFT, GME); a listing on another exchange is MIC:TICKER (XPAR:AIR).
statementNoStatement: 'income' (income statement), 'balance' (balance sheet), or 'cashflow' (cash-flow statement); the aliases 'is'/'p&l', 'bs' and 'cf' also work. Defaults to income.income

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint, so the description carries the main behavioral burden and adds substantial context: SEC XBRL sourcing, latest-restated value selection for one exact period end, and the discrete-quarter derivation rule marked as Derived. It also discloses scope exclusions, which is valuable for avoiding misuse.

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

Conciseness5/5

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

Four dense sentences front-load the core purpose and source, followed by return behavior, derivation logic, and exclusions. Every sentence adds distinct routing or behavioral information with no 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?

For a read-only statement tool with no output schema, the description is unusually complete: it explains purpose, data source, return scope, derivation behavior, and explicit alternatives. Combined with the readOnlyHint annotation, nothing material is missing.

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 description coverage is 100%, so the schema already documents ticker, year, period, and statement with formats and defaults. The description adds conceptual context but no new parameter syntax or constraints beyond what the schema provides, so baseline 3 is appropriate.

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?

States a specific verb and resource: get a company's income statement, balance sheet, or cash-flow statement for a fiscal year and period. It also names the data source and explicitly differentiates from siblings like GetRevenueBreakdown and GetFinancialFact, so an agent can select it without opening other schemas.

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

Usage Guidelines5/5

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

Provides explicit when-to-use and when-not-to-use guidance: company-specific dimensional facts are excluded, and it routes segment/geographic revenue to GetRevenueBreakdown and single-line-item comparisons to GetFinancialFact or CompareFinancialFact. It also clarifies the common Q4 reporting pitfall and directs users to FY for annual figures.

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