Skip to main content
Glama
mydata-ag

bexio-mcp

Official
by mydata-ag

bexio Invoices

bexio_invoices
Destructive

Manage bexio invoices with full CRUD and workflow actions: list, search, create, update, delete, issue, cancel, send, copy, and generate PDFs, supporting polymorphic positions.

Instructions

Manage bexio invoices (kb_invoice). Status ids: 7 Draft, 8 Pending, 9 Paid, 16 Partial, 19 Canceled, 31 Unpaid. Actions: "list" (all invoices; optional limit/offset/order_by — orderable by id, total, total_net, total_gross, updated_at), "search" (search_criteria required; searchable fields: id, document_nr, title, contact_id, contact_sub_id, user_id, kb_item_status_id, currency_id, total, total_gross, total_net, is_valid_from, is_valid_to, api_reference, updated_at; optional limit/offset/order_by), "get" (id; returns the invoice including positions), "create" (payload; polymorphic positions array supported — custom, article, text, subtotal, pagebreak, discount), "update" (id + payload of fields to change; positions cannot be updated here), "delete" (id; permanently deletes the invoice — cannot be undone), "issue" (id; draft -> pending), "revert_issue" (id; sets an issued invoice back to draft), "cancel" (id; cancels the invoice — there is no API to un-cancel), "mark_as_sent" (id), "send" (id + email with recipient_email/subject/message, optional mark_as_open/attach_pdf; message must contain "[Network Link]"), "copy" (id + copy with contact_id required; creates a new invoice as a copy), "pdf" (id; optional logopaper for letterhead and save_path to write the PDF to disk instead of returning base64).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoInvoice id (required for every action except list, search and create)
copyNoCopy parameters for "copy"
emailNoEmail parameters for "send"
limitNoMaximum number of results (default 500, max 2000)
actionYesOperation to perform
offsetNoNumber of results to skip (pagination)
payloadNoInvoice fields for "create"/"update"
order_byNoField to order by; append "_desc" for descending (e.g. "id_desc")
logopaperNoFor "pdf": render the PDF on the letterhead paper
save_pathNoFor "pdf": write the PDF to this file path instead of returning base64
search_criteriaNoSearch conditions, combined with logical AND
Behavior5/5

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

The description discloses critical behaviors beyond annotations: 'delete' is irreversible, 'cancel' has no un-cancel API, 'issue' transitions draft to pending, positions cannot be updated via 'update', and send requires '[Network Link]' in the message. These details are not captured by annotations (destructiveHint=true, readOnlyHint=false) and greatly enhance transparency.

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: it starts with the overall purpose and status IDs, then lists each action with its behavior and parameters. Each sentence adds necessary information; no redundancy. Could be slightly more concise by grouping related actions, but the clarity and completeness justify the length.

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 (11 parameters, nested objects, polymorphic positions, 13 actions) and no output schema, the description covers most essential aspects: action purposes, parameter constraints, and some return values (e.g., 'get' returns invoice with positions, 'pdf' returns base64 or file). Missing details on error handling and response formats for other actions, but sufficient for safe invocation.

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% and schema descriptions are detailed, but the description adds context such as: the polymorphic positions array supports six types (custom, article, text, subtotal, pagebreak, discount), searchable fields are listed, and pdf action parameters (logopaper, save_path) are explained. This goes beyond the schema's property descriptions.

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 states 'Manage bexio invoices (kb_invoice)' and enumerates 13 distinct actions (list, search, get, create, update, etc.), each with specific behavior. It clearly distinguishes this tool from siblings like bexio_bills or bexio_quotes by focusing on invoice-specific status IDs and actions.

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?

While there is no explicit comparison to sibling tools, the description provides clear context for when to use each action (e.g., 'list' returns all invoices, 'search' requires criteria). It also includes constraints like the trial period limitation for 'send'. However, it does not discuss prerequisites or alternative tools for similar operations.

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