Skip to main content
Glama
SynderAccounting

gl-importer

Official

import_csv

Import CSV/XLSX accounting data into QuickBooks Online or Xero. Two-step process: first dry-run to preview mapping and missing fields, then confirm to commit the import.

Instructions

Happy-path CSV/XLSX importer. Two-step: first call (without confirmed) auto-resolves the company, uploads the file, and returns the server's proposed mapping plus any missingRequired fields — show this to the user. Re-call with confirmed=true (and the same filePath) to run the real import and poll until it terminates. Returns { stage: 'DRY_RUN' | 'DONE', importId?, status, summary?, proposedMapping?, missingRequired? }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filePathYesAbsolute path to a .csv, .xlsx, or .xls file.
entityNameYesEntity to import as — match list_entities (e.g. 'Journal Entry').
companyIdNoOptional. If omitted and exactly one ACTIVE company exists, it's picked automatically.
confirmedNoSet true on the second call to commit the import. Default false (dry-run only).
timeoutSecondsNoForwarded to wait_for_import on the confirmed call. Default 600.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
stageYesDRY_RUN when confirmed=false (first call); DONE when confirmed=true.
companyIdNo
entityNameNo
importIdNoPresent when stage=DONE.
statusNoFinal import status (stage=DONE).
proposedMappingNoAuto-resolved column→field mapping (stage=DRY_RUN).
missingRequiredNoRequired target fields the auto-mapper could not resolve (stage=DRY_RUN).
summaryNoPer-type result counts when stage=DONE and the import reached a terminal state.
hintNoNext-step hint for the LLM.
Behavior5/5

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

The description adds significant behavioral context beyond annotations: it explains the two-step call, polling, default timeout forwarding, and auto-company detection. Annotations indicate non-read-only, non-destructive behavior; description confirms with details.

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 well-structured with a clear opening sentence, step-by-step instructions, and return value format. It is relatively concise for the complexity, though could trim minor details.

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 complexity (two-step workflow, optional auto-detection, output schema), the description covers the essential workflow and return shape. It lacks edge cases but is adequate for the happy path.

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?

Input schema covers all 5 parameters with descriptions (100% coverage). The description adds value by explaining the role of 'confirmed' in the two-step process and that 'timeoutSeconds' is forwarded to wait_for_import, improving semantic understanding.

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 tool's purpose: 'Happy-path CSV/XLSX importer' and explains the two-step process of dry-run then commit. It distinguishes itself from sibling tools like auto_import by detailing the sequential workflow.

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

Usage Guidelines4/5

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

The description provides clear guidance on when to use the tool and how to use it step-by-step (first call without confirmed, then with confirmed). However, it does not explicitly mention when not to use it or compare it to alternatives like auto_import.

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/SynderAccounting/gl-importer-plugin'

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