Skip to main content
Glama
mydata-ag

bexio-mcp

Official
by mydata-ag

bexio Manual Entries

bexio_manual_entries
Destructive

List, create, update, or delete manual accounting entries and their attached files in bexio accounting.

Instructions

Manage manual accounting entries (bookings) and their attached files (bexio accounting 3.0 API). Actions: "list" (all manual entries; optional limit/offset), "create" (payload required: type — manual_single_entry/manual_compound_entry/manual_group_entry —, date, entries array with debit_account_id, credit_account_id, tax_id, tax_account_id, description, amount, currency_id, currency_factor), "update" (id + payload; PUT replaces the entry, so send type, date and the full entries array; locked entries — is_locked=true — cannot be edited), "delete" (permanently delete a manual entry by id — cannot be undone), "next_reference_number" (reference number suggested for the next manual entry). File actions cover BOTH scopes: with entry_id they target a single entry LINE (types manual_single_entry/manual_group_entry); without entry_id they target the COMPOUND entry itself (type manual_compound_entry). "list_files" (id, optional entry_id, optional limit/offset), "get_file" (id + file_id, optional entry_id; returns the file content — pass save_path to write it to disk instead of returning base64 inline), "add_file" (id, optional entry_id, plus file_path OR content_base64 + file_name; uploads multipart/form-data, max 12MB, formats PNG/JPG/JPEG/GIF/DOC/DOCX/XLS/XLSX/PPT/PPTX/PDF), "delete_file" (id + file_id, optional entry_id; removes the connection between file and entry — cannot be undone).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoManual entry id (required for update/delete and all *_file actions)
limitNoMax results for "list"/"list_files"
actionYesOperation to perform
offsetNoResults to skip for "list"/"list_files"
file_idNoFile id (required for get_file/delete_file)
payloadNoManual entry fields. Required on create and update (PUT sends the full entry): type, date, entries.
entry_idNoId of a single entry LINE within the manual entry. Provide it for *_file actions on entry lines (manual_single_entry/manual_group_entry); omit it to address files of a manual_compound_entry.
file_nameNoFor "add_file": file name to upload as (defaults to the basename of file_path)
file_pathNoFor "add_file": path of a local file to upload
save_pathNoFor "get_file": write the file to this path instead of returning base64 content inline
content_base64NoFor "add_file": base64-encoded file content (alternative to file_path; requires file_name)
Behavior5/5

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

The description discloses key behaviors: delete is permanent, update is a full PUT replacement, file uploads have size (12MB) and format limits, and the scope differentiation for file actions (entry_id vs compound entry). These complement the annotations (destructiveHint true, readOnlyHint false) without contradiction.

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 relatively long but well-structured by action, with clear grouping of entry and file operations. It front-loads the overall purpose. While verbose, the complexity of 9 actions justifies the length; every sentence contributes useful information.

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?

The description covers all actions, explains return behavior (e.g., file content vs inline base64), and details file upload constraints. It lacks explicit return schemas for list/create/update but compensates with behavioral notes. For a complex tool with no output schema, it is adequately complete.

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?

Schema coverage is 100% with descriptive fields, so baseline is 3. The description adds value by explaining the 'type' enum meanings (single, compound, group), the update requirement to send full payload, and the entry_id scope for files. This provides meaningful context beyond the schema alone.

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 manages manual accounting entries and their attached files, listing all 9 actions with specific verbs (list, create, update, delete, get file, etc.). It distinguishes entry-level vs file-level operations and mentions the API version, providing precise purpose.

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 explains when to use entry_id vs not for file actions, and notes that locked entries cannot be edited. However, it does not explicitly compare this tool to sibling tools like bexio_bills or bexio_accounting, which handle similar accounting data. The domain is implicit from the title and scope.

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/mydata-ag/bexio-mcp'

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