Skip to main content
Glama

upload_accounting_import

Import a JOURNAL EXPORT (CSV/Excel) from another accounting system (source_system, e.g. bexio, abacus) and match it against the bank entries. file_base64 is the file's raw bytes, base64.

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": {
      "company_id": "<company_id>",
      "filename": "<filename>",
      "file_base64": "<file_base64>",
      "source_system": "<source_system>"
    },
    "name": "upload_accounting_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYes
company_idYes
file_base64Yes
source_formatNo
source_systemYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, yet it omits the important behavioral facts. It never says whether importing creates journal entries, whether the match against bank entries is automatic or proposed, whether re-running is idempotent, or what happens to unmatched rows.

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?

Two sentences, front-loaded with the operation and its purpose, with no filler. The awkward line breaks and formatting artifacts cost it a little, but nothing is wasted.

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

Completeness1/5

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

For a 5-parameter mutation tool with zero annotations, no output schema, and no parameter documentation in the schema, the description is far too thin. An agent would not know what gets created, how matching is resolved, or what source_format values are acceptable.

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

Parameters2/5

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

Schema description coverage is 0% for 5 parameters, and the description compensates for only two: it clarifies that file_base64 is raw bytes, base64, and gives examples (bexio, abacus) for source_system. filename, company_id, and especially source_format remain fully undocumented in both places.

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 gives a specific verb and resource — import a journal export (CSV/Excel) from another accounting system and match it against bank entries — so the agent knows exactly what operation it performs. It does not distinguish this from the close sibling upload_accounting_document, so the agent must guess which of the two upload paths applies.

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?

Usage is only implied by the format constraint: the file must be a journal export CSV/Excel from a foreign accounting system. There is no statement of when to prefer this over upload_accounting_document or upload_document, no prerequisites, and no 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.

Resources