Skip to main content
Glama
mydata-ag

bexio-mcp

Official
by mydata-ag

bexio Orders

bexio_orders
Destructive

Manage sales orders with actions to list, search, create, update, delete, generate PDFs, and set up recurring repetitions. Create delivery notes or invoices directly from an order.

Instructions

Manage sales orders (kb_order) including recurring-order repetitions and documents derived from an order. Actions: "list" (all orders, optional limit/offset/order_by: id, total, total_net, total_gross, updated_at), "search" (search_criteria required; supported fields: id, kb_item_status_id (5 Pending, 6 Done, 15 Partial, 21 Canceled), document_nr, title, contact_id, contact_sub_id, user_id, currency_id, total_gross, total_net, total, is_valid_from, is_valid_to, updated_at), "get" (order by id, includes positions), "create" (payload; no field is formally required but usually at least contact_id and user_id; positions may be included), "update" (id + payload of fields to change; positions cannot be updated here), "delete" (permanently delete the order by id — cannot be undone), "pdf" (render the order as PDF; optional logopaper for letterhead, optional save_path to write to disk), "get_repetition" (show the recurring-order configuration), "edit_repetition" (id + repetition payload: start, optional end, repetition rule of type daily/weekly/monthly/yearly), "delete_repetition" (stop the recurring order — cannot be undone), "create_delivery" (create a delivery note from the order; optional positions array, omit to copy all positions), "create_invoice" (create an invoice from the order; optional positions array, omit to copy all positions).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoOrder id (required for every action except "list", "search" and "create")
limitNoMaximum number of results (default 500, max 2000)
actionYesOperation to perform
offsetNoNumber of results to skip (pagination)
payloadNoOrder fields. The API marks no field as strictly required on create, but at least contact_id and user_id are typically needed. Updates cannot change positions (use the document-positions tool).
order_byNoField to order by; append "_desc" for descending (e.g. "id_desc")
logopaperNoFor "pdf": render the PDF on the letterhead paper
positionsNoPositions to copy into the new document; omit to copy ALL positions from the order
save_pathNoFor "pdf": write the PDF to this file path instead of returning base64 inline
repetitionNoRecurring-order configuration. Required: start, repetition (end may be null for indefinite runs).
search_criteriaNoSearch conditions, combined with logical AND
Behavior4/5

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

Beyond annotations (destructiveHint=true), the description warns about irreversible actions ('cannot be undone' for delete and delete_repetition) and mentions limitations (positions cannot be updated). This adds valuable behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is comprehensive but somewhat lengthy, listing all actions with details. While structured and front-loaded, some redundancy exists (e.g., repeating 'cannot be undone'). Could be trimmed for brevity.

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, no output schema), the description covers key constraints, action-specific notes, and edge cases. It is sufficiently complete for an agent to use correctly.

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?

With 100% schema coverage, the description adds crucial nuances: e.g., 'no field is formally required but usually at least contact_id and user_id', and details the repetition object structure. This goes beyond the schema's base definitions.

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 sales orders (kb_order) and enumerates all specific actions (list, search, get, create, etc.), making the purpose unambiguous and distinguishing it from sibling tools like bexio_document_positions or bexio_invoices.

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 context for each action, e.g., 'positions cannot be updated here' and 'delete permanently'. However, it does not explicitly tell when to use alternative tools (e.g., bexio_document_positions for updating positions), leaving room for ambiguity.

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