Skip to main content
Glama

Balance sheet

accounting_balance_sheet
Read-onlyIdempotent

Balance sheet as at a date: assets, liabilities and equity per account, including profit to date not yet closed off. Read-only. Needs the user's GetAccountED sign-in (they are asked to sign in the first time).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "accounting_balance_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_atNoDate YYYY-MM-DD (default: today)
business_idNoAccounting practices only: which client's books (an id from accounting_list_my_businesses). Leave out to use the books chosen at sign-in.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered structurally. The description's genuine addition is the authentication prerequisite (GetAccountED sign-in, prompted on first use), which is real behavioral context not present in annotations. It adds nothing about default date handling or response shape beyond the schema.

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?

Three short clauses, front-loaded with what the report contains, then the read-only and auth facts. No filler, no repetition of the title, nothing that could be cut without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, zero-required report tool with no output schema, the description covers content, date semantics, and the auth gate, which is close to sufficient. It could say more about what a returned balance sheet looks like (single object vs. rows per account) given there is no output schema to fall back on.

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 coverage is 100% and both parameters are documented in-schema, including the business_id fallback to the sign-in-selected books and the today default for as_at. The description adds only a restatement of the date scoping and the "per account" granularity, so baseline 3 applies.

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

Purpose4/5

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

Names a specific resource (balance sheet) and enumerates its contents — assets, liabilities, equity per account, plus unclosed profit to date — which is more than the title alone conveys. It stops short of distinguishing itself from adjacent report siblings such as accounting_trial_balance or accounting_profit_and_loss, so an agent must infer the boundary.

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

Usage Guidelines3/5

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

The "as at a date" phrasing implies the as-of reporting use case, and the sign-in note tells the agent a first-call auth prompt may occur. There is no explicit guidance on when to prefer this over trial balance, P&L, or overview, and no statement of exclusions.

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.