Skip to main content
Glama

xero_reports_balance_sheet

Retrieve a Balance Sheet report as of a specific date. Displays assets, liabilities, and equity to assess financial position.

Instructions

Get a Balance Sheet report as of a specific date.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesReport date in YYYY-MM-DD format (required)

Implementation Reference

  • Tool definition (schema) for xero_reports_balance_sheet — accepts a 'date' string in YYYY-MM-DD format.
    {
      name: "xero_reports_balance_sheet",
      description: "Get a Balance Sheet report as of a specific date.",
      inputSchema: {
        type: "object",
        properties: {
          date: {
            type: "string",
            description: "Report date in YYYY-MM-DD format (required)",
          },
        },
        required: ["date"],
      },
    },
  • Handler for xero_reports_balance_sheet — calls the Xero API endpoint Reports/BalanceSheet with the provided date and returns the result.
    case "xero_reports_balance_sheet": {
      const { date } = args as { date: string };
      const response = await client.get("Reports/BalanceSheet", { date });
      return {
        content: [{ type: "text", text: JSON.stringify(response, null, 2) }],
      };
    }
  • src/index.ts:195-198 (registration)
    The tool is registered via ListToolsRequestSchema handler which returns all tools including reportTools (which contains xero_reports_balance_sheet).
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      const domainTools = getAllDomainTools();
      return { tools: [navigateTool, statusTool, backTool, ...domainTools] };
    });
  • src/index.ts:267-269 (registration)
    Routing: tool calls starting with 'xero_reports_' are dispatched to handleReportTool, which handles xero_reports_balance_sheet.
    if (name.startsWith("xero_reports_")) {
      return await handleReportTool(name, toolArgs);
    }
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only mentions getting a report, missing details like read-only nature, data scope, or any side effects. This is insufficient for a tool with no annotation support.

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?

The description is a single, concise sentence that directly states the tool's purpose without any extraneous information. Every word earns its place.

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?

Given the tool's low complexity (one parameter, no output schema), the description is largely sufficient, though it could optionally mention the report contents (e.g., assets, liabilities). It meets the minimum requirements for an agent to understand its use.

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?

The input schema has 100% description coverage and the one parameter ('date') is adequately described in the schema. The description adds no extra semantic value beyond the schema, so baseline score of 3 is appropriate.

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 description clearly states the action ('Get') and the specific resource ('Balance Sheet report') with a qualifier ('as of a specific date'). It distinguishes this tool from sibling report tools (e.g., aged payables, profit and loss) by naming the report type uniquely.

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 description implies use for obtaining a balance sheet at a given date but does not explicitly state when to use this versus other report tools or provide any exclusions or context for alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wyre-technology/xero-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server