Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-bexio

by AIWerk

update_purchase_order

Idempotent

Update a single purchase order in Bexio by changing its fields, such as contact, currency, language, and document settings.

Instructions

Update a single purchase order

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoThe id of the purchase order
mailNoThe mail address of the company
titleNo
footerNo
headerNo
user_idNoReferences a [user object](#operation/v3ListUsers)
currencyNo
languageNo
mwst_typeNoPossible values are * `included` - included means that the tax is included in the total price * `excluded` - excluded means that the tax is excluded from the total price * `exempt` - exempt means that no tax is charged
referenceNoA reference which can be added to the document by the client.
contact_idNoReferences a [contact object](#operation/v2ListContacts)
created_atNoCreation date of the purchase order
project_idNoReferences a [project object](#operation/v2ListProjects)
updated_atNoLast time when purchase order was updated
currency_idNoReferences a [currency object](#operation/ListCurrencies)
date_formatNo
document_nrNo
is_valid_toNo
language_idNoReferences a [language object](#operation/v2ListLanguages)
mwst_is_netNoThis value affects the total if the field `mwst_type` has been set to 0.<br> `false` = Taxes are included in the total<br> `true` = Taxes will be added to the total
logopaper_idNo
api_referenceNoThis field can only be read and edited by the api. It can be used to save references to other systems.
is_valid_fromNo
template_slugNo
contact_sub_idNoReferences a [contact object](#operation/v2ListContacts)
is_valid_untilNo
bank_account_idNoReferences a [bank account object](#operation/ListBankAccounts)
is_compact_viewNo
payment_type_idNoReferences a [payment type object](#operation/v2ListPaymentTypes)
salesman_user_idNoReferences a [user object](#operation/v3ListUsers)
nb_decimals_priceNoThe maximum number of decimal digits to display for prices (line item prices, totals, etc.).
purchase_order_idYesthe id of the purchase order
nb_decimals_amountNoThe maximum number of decimal digits to display for amounts (number of items).
custom_translationsNo
show_position_taxesNo
delivery_address_typeNo
terms_of_payment_textNoAdditional text which is displayed below the terms of payment
contact_address_manualNoThe contact address for the document. Newlines are in the format `\n`
kb_payment_template_idNo
delivery_address_manualNoThe delivery address for order. Newlines are in the format `\n`
Behavior2/5

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=true. The description adds no additional behavioral context, such as whether unspecified fields are preserved, required permissions, or return value. It just restates the obvious 'update' action.

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

Conciseness5/5

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

The description is a single sentence with no filler or redundant information. It front-loads the action and resource, making it highly concise and easy to parse.

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?

For a tool with 40 parameters, nested objects, and no output schema, the one-sentence description is severely lacking. It gives no operational context, no common use cases, and no indication of input expectations beyond the schema itself.

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

Parameters2/5

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

With 40 parameters and 57% schema coverage, the description provides no additional meaning for any parameter. It does not mention which fields are updatable, how to identify the purchase order, or any relationships between parameters.

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 action 'Update' and the resource 'purchase order', distinguishing it from create, delete, get, and list sibling tools. 'Single' clarifies that it operates on one purchase order at a time.

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 provides no guidance on when to use this tool versus alternatives like create_purchase_order or update_quote. It simply states the operation without any context on prerequisites, alternatives, or exclusions.

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