Skip to main content
Glama
mydata-ag

bexio-mcp

Official
by mydata-ag

bexio Expenses

bexio_expenses
Destructive

Manage business expenses by listing, creating, updating, and deleting expense records with support for filtering, pagination, and status transitions.

Instructions

Manage expenses (bexio 4.0 API). Expense ids are UUID strings. Actions: "list" (paginated via limit/page/order/sort; filters: vendor, gross_min/max, net_min/max, paid_on_start/end, created_at_start/end, title, currency_code, document_no, supplier_id, project_id), "get" (expense by id), "create" (payload required: paid_on, currency_code, amount, attachment_ids; optional supplier, bank/booking account, tax and address fields), "update" (id + full payload; same required fields as create), "delete" (id; permanently deletes the expense — cannot be undone), "execute_action" (id + expense_action "DUPLICATE": copies the expense into a new draft), "update_status" (id + status: "DONE" completes the expense, "DRAFT" reverts it to draft), "validate_document_number" (document_no; reports whether it is available and the next free number).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoExpense id (UUID; required for get/update/delete/execute_action/update_status)
pageNoPage number for "list"
sortNoField to sort by for "list"
limitNoResults per page for "list" (max 500)
orderNoSorting order for "list"
actionYesOperation to perform
statusNoTarget status for "update_status"
filtersNoOptional filters for "list"
payloadNoExpense fields. Required on create and update: paid_on, currency_code, amount, attachment_ids. Update sends the full expense (fields left out are cleared).
document_noNoDocument number to check for "validate_document_number"
expense_actionNoAction to execute for "execute_action"
Behavior4/5

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

Annotations include destructiveHint=true and readOnlyHint=false. The description adds value by noting that delete 'permanently deletes the expense — cannot be undone' and that update 'sends the full expense (fields left out are cleared)'. These specifics go beyond the annotations and clarify behavioral traits.

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 a single paragraph that is moderately concise but could be more structured (e.g., bullet points for actions). It front-loads the overall purpose but becomes dense. Every sentence adds value, but readability could be improved.

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

Completeness2/5

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

No output schema is provided, and the description omits details on return values, error handling, or authentication requirements. For a tool with 11 parameters, nested objects, and multiple actions, the description is incomplete for an AI agent to reliably invoke without additional context.

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

Parameters3/5

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

Schema description coverage is 100% with detailed parameter descriptions. The description adds some context (e.g., UUID ids, required fields for create/update, full payload behavior), but does not significantly enhance meaning beyond the schema. Baseline 3 is appropriate.

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 it manages expenses via the bexio 4.0 API, listing multiple specific actions (list, get, create, update, delete, etc.) with brief explanations. This distinguishes it from sibling tools like bexio_bills or bexio_invoices, which cover different domains.

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?

The description provides action-specific parameter requirements (e.g., list uses pagination/filters, create requires payload with specified fields), offering some guidance. However, it does not explicitly state when to use this tool vs alternatives, nor does it provide exclusions or comparative context with sibling tools.

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