Skip to main content
Glama

Silicon Floor

by com.siliconfloor
OverviewDiscussionsAdmin

Financial statements as filed

get_financials
Read-only

Returns a company's income statement, balance sheet and cash flow statement as filed with the SEC in XBRL: the last 12 calendar quarters or the last 6 fiscal years, 30+ lines, with the filing behind each period. Use it when the user asks for a company's revenue, earnings, balance sheet or cash flow over several periods. Lines computed from filed lines say how (computed); a null is a line the company did not file for that period: report it as unknown. Cash outflows (capex, buybacks, dividends paid) are negative. A foreign private issuer files once a year (20-F): its statements are fiscal years whatever the basis asked — unless it files its quarterly statements as Form 6-K (ASML, Nebius, STMicro and others): those quarters are included, each with its 6-K and audited: false. Amounts are in the filing currency. For a foreign issuer that publishes its quarters only in releases filed as Form 6-K (TSMC), releases adds its monthly revenue, quarterly results and guidance — unaudited, and kept apart from the statements. revenueBy breaks revenue down by segment, geography and product as the company's own tables present it (only tables whose lines add up to the total filed), and customerConcentration lists the customers it discloses with their share of revenue, labels as filed ("Customer A": a customer the company does not name). statement=breakdowns returns only those two. guidance is what the company's latest earnings release says it expects (revenue, gross margin, eps, each with its basis and period), actualVsGuidance what it then filed against its own guidance, nextEarnings the estimated date of its next results; statement=outlook returns only those.

Input Schema

NameRequiredDescriptionDefault
basisNoquarterly (default: last 12 calendar quarters) or annual (last 6 fiscal years).
symbolYesTicker or company name, e.g. NVDA, AMD, ASML, 'nvidia', 'taiwan semiconductor'. Case-insensitive.
statementNoincome, balance, cashflow, breakdowns (revenue by segment, geography and product, and customer concentration), outlook (the company's guidance, actuals against it, next earnings date) or all (default all).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / statement / description
      Previous value: -"income, balance, cashflow, breakdowns (revenue by segment, geography and product, and customer concentration) or all (default all)."New value: +"income, balance, cashflow, breakdowns (revenue by segment, geography and product, and customer concentration), outlook (the company's guidance, actuals against it, next earnings date) or all (default all)."
    • changedInput schema / properties / statement / enum
      Previous value: -[
-  "income",
-  "balance",
-  "cashflow",
-  "breakdowns",
-  "all"
-]New value: +[
+  "income",
+  "balance",
+  "cashflow",
+  "breakdowns",
+  "outlook",
+  "all"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / statement / description
      Previous value: -"income, balance, cashflow or all (default all)."New value: +"income, balance, cashflow, breakdowns (revenue by segment, geography and product, and customer concentration) or all (default all)."
    • changedInput schema / properties / statement / enum
      Previous value: -[
-  "income",
-  "balance",
-  "cashflow",
-  "all"
-]New value: +[
+  "income",
+  "balance",
+  "cashflow",
+  "breakdowns",
+  "all"
+]
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, non-destructive, closed-world), and the description adds substantial operational detail beyond them: null means the company did not file that line, computed lines are labeled, cash outflows are negative, amounts are in filing currency, and FPI/20-F vs 6-K treatment. This is exactly the extra context the annotations do not carry.

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?

It is front-loaded with the core purpose, but the body is one dense block cramming multiple special cases (20-F, 6-K, ASML/Nebius/STMicro, TSMC releases, guidance trio) without structural breaks. Most content earns its place, yet the density and lack of segmentation cost readability.

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, so the description carries the full return-shape burden and does so thoroughly: period coverage, line count, per-period filing linkage, null semantics, sign conventions, currency, and the alternate breakdowns/outlook modes. An agent has enough to call and interpret it correctly.

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 coverage is 100% so the baseline is 3, and the description still adds real semantic meaning: it explains what statement=breakdowns and statement=outlook return, what revenueBy and customerConcentration expose, and the fiscal-year-vs-quarter behavior of basis for foreign issuers. Labels like 'Customer A' are clarified beyond the schema.

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 (returns income statement, balance sheet, cash flow as filed in XBRL) with scope (last 12 quarters / 6 fiscal years, 30+ lines). It is clearly distinguished from siblings like get_filings and get_company because it enumerates the exact statement content plus derived fields (revenueBy, customerConcentration, guidance).

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?

Explicitly says when to use it: 'Use it when the user asks for a company's revenue, earnings, balance sheet or cash flow over several periods.' It lacks an explicit when-not / named-alternative clause (e.g., pointing to get_filings for raw filings), so it is strong context without exclusion guidance.

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

All Silicon Floor toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources