Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-bexio

by AIWerk

update_bill

Idempotent

Update existing bills in Bexio by modifying supplier, dates, line items, discounts, attachments, and payment info. Choose manual or calculated amounts and split line items as needed.

Instructions

Update Bill

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesid of Bill to update
titleNo
addressYesAddress
paymentNo
due_dateYes
item_netYes
bill_dateYes
discountsYesEach of Discount's 'id' must be unique (no duplicates) and already existing on the Bill or it should be null for creating new Discount. When 'split_into_line_items' is false then there must 0 Discounts.
amount_manNoRequired when 'manual_amount' is true. Maximum of 17 digits and maximum of 2 decimal digits.
line_itemsYesEach of Line Item's 'id' must be unique (no duplicates) and already existing on the Bill or it should be null for creating new Line Item. When 'split_into_line_items' is false then there must be only 1 Line Item.
vendor_refNo
amount_calcNoRequired when 'manual_amount' is false. Maximum of 17 digits and maximum of 2 decimal digits.
document_noNo
supplier_idYes
currency_codeYes
exchange_rateNoRequired when 'currency_code' is different from 'base_currency_code' (taken from settings). Maximum of 5 digits and maximum of 10 decimal digits.
manual_amountYesIndicates whether 'amount_man' or 'amount_calc' is required and considered as bill amount
attachment_idsYes
contact_partner_idYes
base_currency_amountNoMaximum of 17 digits and maximum of 2 decimal digits.
split_into_line_itemsYesIndicates whether Bill has multiple items (true) or single item (false). By items it means 'line_items' and 'discounts'.
Behavior2/5

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

The description discloses no behavioral traits beyond the annotations. While annotations correctly indicate this is a non-read-only, idempotent, non-destructive operation, the description adds no additional context such as side effects, required permissions, or interaction with other bill fields. It does not contradict annotations, but adds no value.

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

Conciseness2/5

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

The description is extremely short, bordering on under-specification. It does not waste words, but one phrase cannot adequately communicate the purpose and usage of a complex tool. It lacks structure and substantive content.

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

Completeness1/5

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

This tool has 21 parameters, 13 required, nested objects, and no output schema. The description is completely inadequate for such complexity, providing no information about return values, field relationships, constraints, or how to correctly structure an update request.

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

Parameters1/5

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

The description contains no parameter information at all. With 21 parameters and only 48% schema description coverage, the description was expected to compensate for undocumented parameters, but it does not. The schema itself provides more meaning than the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Update Bill' is a direct restatement of the tool name (update_bill), providing no additional specificity about what updating a bill entails or how it differs from related tools like create_bill, get_bill, or update_bill_booking. It is a pure tautology.

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

Usage Guidelines2/5

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

The description gives zero guidance on when to use this tool, what prerequisites exist, or how it relates to alternatives such as create_bill or update_bill_booking. There is no mention of scenarios where this tool should or should not be chosen.

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/AIWerk/mcp-server-bexio'

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