stub

Import trial balance

import_trial_balance

Post a trial balance from another package (Xero, Sage, QuickBooks) as the business's opening balances: lines named by account id or name, zero lines dropped, and it becomes the take-on that bank lines before it are cut off at. Refused when the business already has opening balances or a line names no account. Prefer this to save_journal_entry for opening balances.

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": "<date>",
      "lines": "<lines>"
    },
    "name": "import_trial_balance"
  }
}

Input Schema

Name	Required	Description
`date`	Yes	The trial balance's date, YYYY-MM-DD: the day before the business starts its books on stub.
`name`	No	The journal's name; "Opening Balance" when omitted.
`lines`	Yes	One row per account with a balance, as the old package's trial balance lists it.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds real behavioral substance: zero lines are dropped, the import becomes the take-on that bank lines before it are cut off at, and it is refused on existing opening balances or unmatched accounts. It stops short of saying whether an import can be undone or what permissions are needed for a state-changing operation.

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?

Front-loaded with the core action and free of filler, and the alternative is placed last where it is easiest to act on. The middle clause ('the take-on that bank lines before it are cut off at') is grammatically tangled and costs a reread.

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 state-changing tool with no output schema, the definition covers preconditions, side effects on transaction matching, and the sibling alternative. The remaining gaps — reversibility and response shape — are minor but not negligible for an import that sets opening balances.

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?

With 100% schema coverage the baseline is 3, but the description adds meaning beyond the schema: lines may be referenced by account id or old-package name, zero-value lines are silently discarded, and the date becomes the take-on cutoff. It does not clarify how debit/credit pairing is validated, leaving part of the nested line shape implicit.

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 ('Post a trial balance ... as the business's opening balances') with the source systems named, and explicitly contrasts it with save_journal_entry. An agent can distinguish it from the many save_* siblings 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 Guidelines5/5

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

'Prefer this to save_journal_entry for opening balances' names the alternative and the condition that selects it, while 'Refused when the business already has opening balances or a line names no account' states the preconditions that block invocation. Both when-to-use and when-it-fails are covered.

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

All stub 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?