Skip to main content
Glama

Invio Xero MCP

get_xero_balance_sheet

get_xero_balance_sheet
Read-only

Balance Sheet report from Xero for the current organisation, as at a date. Read-only. columns gives the as-at period label(s); rows are flattened from Xero's nested section layout (section names the enclosing group, e.g. "Assets" or "Liabilities"; rowType "SummaryRow" marks a subtotal/total, not a line item). currency comes from this organisation's own Xero settings, never assumed - state it whenever relaying a figure from this report. If date was supplied, Xero reports the balance sheet as at the END OF THAT MONTH, not the exact day given - say "as at [end of month]", not the literal date requested. This organisation's financial year is NOT necessarily the calendar year (added 11 September 2026 - see lib/xero/financial-year.ts). financialYear in the result names the organisation's real financial year end and its exact current/previous dates, or says the year end is unknown. Never answer "this financial year", "last financial year", or "year to date" from the calendar year or the organisation's country - use financialYear's current.toDate (or previous.toDate) as date, and state the period you actually used when relaying a figure.

Input Schema

NameRequiredDescriptionDefault
dateNoAs-at date, YYYY-MM-DD. Xero reports this as at the END of the month containing this date, not the exact day. Omit for today.
organisationNoThe Xero organisation to use, by its display name. Only needed if this connection reaches more than one organisation - omit it when there is only one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A5/5.0
Behavior5/5

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

The description goes far beyond the simple 'readOnlyHint: true' annotation by explaining deep behavioral quirks, such as how Xero flattens nested data into 'columns' and 'rows,' and the complex logic regarding financial year definitions.

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?

While long, the description is highly efficient. Every sentence is dedicated to solving a specific ambiguity (date interpretation, data structure, terminology), preventing potential operational errors during invocation.

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?

Given the complexity of financial reporting and Xero's unique data structure, the description is extremely complete. It covers the data source, the date reporting methodology, and the required output style.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Even though schema coverage is 100%, the description provides vital semantic meaning beyond the schema. It specifies that the 'date' field implies an 'as-at end of month' report, and clarifies the role of the 'organisation' parameter in multi-tenant scenarios.

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 tool's purpose is immediately clear: retrieving a Balance Sheet report from Xero. It is specific and distinct from other listed sibling tools like P&L or general report queries.

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?

The description provides crucial usage guidelines by detailing how Xero interprets the request (e.g., stating that date input results in an 'as at the end of month' report) and strictly forbidding common calendar-based phrasing.

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