Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-bexio

by AIWerk

update_item_position

Update an existing item position on a Bexio quote, order, or invoice by modifying details like price, quantity, tax, or discount.

Instructions

Edit an item position

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNo
amountNo
tax_idNoReferences a [tax object](#operation/ListTaxes) Please note that only active sales taxes can be used as references on the document types `quote`, `order` and `invoice`. An easy way to retrieve all valid taxes is by calling the taxes endpoint with the query parameters `types=sales_tax&scope=active` (
unit_idNoReferences a [unit object](#operation/v2ListUnits)
account_idNoReferences an [account object](#operation/ListAccounts)
article_idNoReferences an [item object](#operation/v2ListItems)
unit_priceNoThe price of one unit (max. 6 decimals)
amount_openNo
document_idYesthe id of the document. E.g. if the `kb_document_type` is set to `kb_invoice` the `document_id` must be set to the ID of the invoice
is_optionalNoOnly valid in the case of Quotes or Orders
position_idYesthe id of the position
amount_reservedNo
amount_completedNo
kb_document_typeYesThe type of the document. Item positions can be added to quotes, orders and invoices
discount_in_percentNoThe discount (max. 6 decimals)
Behavior2/5

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

The description adds nothing beyond the annotations. readOnlyHint=false already indicates mutation, but the description does not disclose side effects (e.g., recalculating document totals), required permissions, or constraints. No contradiction exists.

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 under-specified, not concise. 'Edit an item position' basically restates the tool name and offers no additional structural value. It is too terse to be useful.

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?

Given 15 parameters, no output schema, and a mutating operation, this single sentence is grossly incomplete. It does not explain required fields, what can be updated, or update semantics, making it insufficient for safe invocation.

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?

The description provides zero parameter-level meaning. While the schema covers many parameters (tax_id, unit_id, document_id, etc.), several like text, amount, amount_open, and amount_reserved remain undocumented. The description fails to compensate for this 67% coverage gap.

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 an item position' clearly identifies the action (edit/update) and resource (item position), but it does not distinguish from sibling position-update tools like update_subposition or update_discount_position. It is clear but lacks sibling differentiation.

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 the relevant document types (quotes, orders, invoices) or contrast with update_subposition/update_text_position, leaving the agent to infer usage from the schema.

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