Skip to main content
Glama

BillTally

Format Multi-Tab Excel or Accounting CSV Spreadsheet

export_ledger_bundle
Read-onlyIdempotent

Statelessly formats checked supplier bills in memory into a multi-tab Microsoft Excel (.xlsx) workbook with SUM and ROUND accounting formulas, or a clean CSV spreadsheet preview.

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": {
      "documents": "<documents>"
    },
    "name": "export_ledger_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoSpreadsheet output format: xlsx (3-tab Excel workbook with live formulas), csv, or quickbooks_csv.xlsx
api_keyNoOptional BillTally Pro API key.
documentsYesList of checked supplier bill objects returned by extract_financial_documents.
bundle_nameNoLabel for the formatted Excel or CSV spreadsheet output.billtally_ledger
reconciliationNoOptional bank statement matching report returned by reconcile_invoices_with_bank_ledger.
use_corrected_amountsNoWhen true, formats the spreadsheet using verified true math totals instead of overcharged billed figures.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavior beyond annotations, notably stateless in-memory formatting and live SUM/ROUND formulas, but it does not explain the return mechanism, authentication needs, or how the output file is delivered.

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?

The description is a single front-loaded sentence with no filler. It is slightly dense, and 'statelessly' and 'in memory' are partly redundant, but the core purpose and output modes are easy to parse.

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

Completeness3/5

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

For a 6-parameter tool with nested objects and no output schema, the definition should clarify what the call returns, such as file bytes, a file URL, or a structured object. The description names the formatted artifacts but does not specify the return shape or the prerequisite relationship with extract_financial_documents, leaving an important gap.

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 description coverage is 100%, so the baseline is 3. The description reinforces that the output is a multi-tab Excel workbook or CSV preview, but it does not add meaning beyond the schema for parameters such as use_corrected_amounts, reconciliation, bundle_name, or api_key.

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?

The description states a specific verb, resource, and output artifact: it formats checked supplier bills into an .xlsx workbook with accounting formulas or a CSV preview. It clearly distinguishes the two output modes, but it does not distinguish this tool from siblings such as audit_and_export_pack.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance or when-not-to-use guidance, and no sibling alternative is named. The only implied choice is between xlsx and CSV via the format parameter, leaving the agent to infer when this export should be used instead of related tools.

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