Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-bexio

by AIWerk

update_quote

Update an existing quote in Bexio by modifying its details, such as dates, contact, currency, taxes, and payment terms.

Instructions

Edit a quote

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNo
footerNo
headerNo
user_idNoReferences a [user object](#operation/v3ListUsers)
quote_idYesthe id of the quote
mwst_typeNo| value | description | |-----|------| | 0 | including taxes | | 1 | excluding taxes | | 2 | exempt from taxes |
contact_idNoReferences a [contact object](#operation/v2ListContacts)
currency_idNoReferences a [currency object](#operation/ListCurrencies)
document_nrNoCan not be used if “automatic numbering” is activated in frontend-settings. Required if “automatic numbering” deactivated. https://help.bexio.com/s/article/000001784
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
pr_project_idNoReferences a [project object](#operation/v2ListProjects)
template_slugNoReferences a [document template slug](#operation/v3ListDocumentTemplate)
contact_sub_idNoReferences a [contact object](#operation/v2ListContacts)
is_valid_untilNo
bank_account_idNoReferences a [bank account object](#operation/ListBankAccounts)
payment_type_idNoReferences a [payment type object](#operation/v2ListPaymentTypes)
show_position_taxesNo
viewed_by_client_atNo
delivery_address_typeNo| value | description | |-------|-------------| | 0 | use invoice address | | 1 | use custom address |
contact_address_manualNoThis field can be used to set a contact address manually. If not in use or `null` the invoice address of the contact will be taken.
delivery_address_manualNoThis field can be used to set a delivery address manually if `delivery_address_type` is set to `1`. If not in use or `null` the invoice address will be taken.
kb_terms_of_payment_template_idNo
Behavior2/5

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

The description adds no behavioral context beyond what the annotations already convey (read-write, non-destructive). It does not disclose side effects, update semantics (e.g., partial vs. full replacement), or any prerequisites like required permissions. Annotations are present but the description fails to enrich them.

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, but it is under-specified rather than appropriately concise. For a tool with 26 parameters and complex behaviors, a two-word description is inadequate and fails to convey essential information.

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?

Despite the rich schema, the description is minimal and leaves the agent to infer behavior. It does not explain the effect of the update, whether partial updates are allowed, or what the response contains. Given the tool's complexity and the absence of an output schema, the description is not complete enough.

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 26 parameters and schema description coverage at 65%, the description should compensate for undocumented fields, but it does not. It mentions no parameters at all, leaving the schema as the only source of information. The required quote_id is not highlighted in the description.

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

Purpose4/5

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

The description 'Edit a quote' clearly states the verb (edit) and resource (quote), making it obvious what the tool does. However, it does not differentiate this from sibling tools like issue_quote, copy_quote, or update_invoice by explaining scope or specific capabilities.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention that it is the primary method for modifying quote fields, nor does it reference related commands like create_quote or issue_quote.

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