YESbusiness

Balance sheet

get_balance_sheet

Read-onlyIdempotent

The balance sheet: what the company owns and owes as balances up to one date (date_until), as a nested tree of account groups and accounts. Sign convention in the raw values: assets are POSITIVE, liabilities and equity NEGATIVE — that is how the report is built, not an error, so talk about amounts held or owed instead of reading a minus sign out loud. The passive side also carries three synthetic rows, identified by a string id: 'yearly_result' (the provisional result of the open accounting year(s), negated like the rest of the passive side, so a profit shows as a negative value), 'currency_revaluation' (unbooked foreign-currency revaluation) and 'total_passive' (liabilities and equity including those results). Set compare_date to add the second period and the difference. The tree is PRE-SUMMED by the server: a group row's values already include every account under it, so read a total off the group row itself and never add child rows up yourself. Every amount is an integer in CENTS of the company's home currency — divide by 100 and present francs with two decimals, never the raw integer. Each row has values.period_1 (the main period), plus values.period_2 and values.difference (period_1 - period_2) only when compare dates were sent.

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": {
      "date_until": "<date_until>",
      "company_id": "<company_id>"
    },
    "name": "get_balance_sheet"
  }
}

Input Schema

Name	Required	Description
`company_id`	Yes	The company to work on — one of list_my_companies' company_id values.
`date_until`	Yes	Report date, YYYY-MM-DD: balances of all bookings up to and including it.
`compare_date`	No	Second report date, YYYY-MM-DD — adds period_2 and difference to every row.
`show_all_accounts`	No	Include accounts with no bookings (zero balances). Leave off unless the user asks about an account that is missing.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description still adds substantial behavior the annotations cannot: assets positive and liabilities/equity negative by construction, the three synthetic passive rows ('yearly_result', 'currency_revaluation', 'total_passive'), and a server-side pre-summed tree so group rows must not be added up manually. These are exactly the traps that cause an agent to misreport figures.

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?

Purpose and sign convention are front-loaded, and virtually every clause carries operational information (units, summing rule, synthetic rows). It is one very dense paragraph, though, and would scan better split into purpose, sign convention, and return-shape sections rather than a single block.

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, so the description must carry the return format and it does: the tree structure, row value fields (period_1/period_2/difference), the cents-integer unit with a presentation rule, and the pre-summed semantics. Nothing an agent needs to read this report 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 all four parameters; the baseline would be 3. The description still adds meaning beyond it, notably that difference is period_1 - period_2 and that period_2/difference appear only when compare dates were sent, plus the rationale behind show_all_accounts.

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 opening sentence names a specific report ('the balance sheet: what the company owns and owes as balances up to one date') and immediately characterizes the return shape as 'a nested tree of account groups and accounts'. That is enough to separate it from get_income_statement or get_account_statement without opening a 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 gives conditional guidance for the optional parameters: set compare_date to add a second period and the difference, and leave show_all_accounts off 'unless the user asks about an account that is missing'. It does not explicitly route the agent away from sibling reports like get_income_statement, but the usage context is clear.

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

All YESbusiness tools Inspect

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

Need Help?