Skip to main content
Glama

analyze_balance_sheet

Read-only

Take a Balance Sheet CSV export from QuickBooks Online, Xero, Zoho Books, or Wave (source auto-detected) and run three checks: (1) bs.equation_broken — the fundamental accounting equation Assets = Liabilities + Equity does not hold (every downstream ratio analysis is invalid until fixed); (2) bs.negative_asset — Cash / AR / Inventory line items with negative balances (reconciliation error signal); (3) bs.negative_equity — Total Equity < 0 (insolvency signal). Input is raw CSV text of a Balance Sheet (Reports → Balance Sheet in QBO / Xero / Zoho / Wave). Max 5,000 rows; max 5 MB. Returns flags with severity, totals (totalAssets, totalLiabilities, totalEquity, equationBalances boolean), and a shareable URL. Use this when a user pastes a Balance Sheet and asks "does my balance sheet balance?", "is the accounting equation satisfied?", or "is my company solvent on paper?". A Balance Sheet that fails Assets = Liabilities + Equity invalidates every downstream financial-ratio analysis — this is the single most important check for any BS.

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": {
      "csvText": "<csvText>"
    },
    "name": "analyze_balance_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvTextYesRaw CSV text of a Balance Sheet report. Works with QuickBooks Online (Reports → Balance Sheet), Xero (Reports → Balance Sheet), Zoho Books (Reports → Balance Sheet), and Wave (Reports → Balance Sheet). Statement should include Total Assets, Total Liabilities, and Total Equity rows. Source is auto-detected from section name signatures.
fileNameNoOptional filename for the share-page label.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), yet the description adds real value: source auto-detection across four products, hard limits (5,000 rows / 5 MB), what the response contains (flags with severity, totals, equationBalances boolean), and a shareable URL. The only gap is that it does not say whether the generated share URL is public or persistent, which matters for a tool that emits a link to financial data.

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 action and the three checks are front-loaded and the size/return details follow in a logical order. It loses a point for redundancy: the closing sentence re-argues that a broken equation invalidates downstream ratio analysis, which was already stated parenthetically under check (1).

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?

There is no output schema, and the description compensates by naming the response payload (severity-tagged flags, four totals, equationBalances boolean, share URL). For a two-parameter analysis tool with supported sources, input limits, and trigger conditions all covered, nothing an agent needs to call 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?

Schema coverage is 100%, so the schema already documents both csvText and fileName, and the description largely restates the CSV-input requirement. It does add meaning beyond the schema with the 'max 5,000 rows' constraint (the schema only enforces a 5 MB maxLength) and the explicit note that headers must include Total Assets/Liabilities/Equity rows.

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 ('Take a Balance Sheet CSV export ... and run three checks') and enumerates the three named checks (bs.equation_broken, bs.negative_asset, bs.negative_equity) with their meanings. The 'Balance Sheet' resource scoping distinguishes it from siblings like analyze_trial_balance and analyze_profit_loss without ambiguity.

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 explicit triggering context with quoted user questions ('does my balance sheet balance?', 'is my company solvent on paper?') and the input precondition (pasted BS export). It does not name an alternative tool or state when-not to use it, but the resource scoping makes misuse unlikely.

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