Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-bexio

by AIWerk

create_item_position

Add an item position to quotes, orders, or invoices in Bexio, including article, unit price, tax, and discount.

Instructions

Create 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
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 no behavioral context beyond what the annotations already convey (write operation). It does not mention side effects, validation rules, or that positions are added to quotes/orders/invoices.

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 to the point of being unhelpful. It is a single phrase that offers no information beyond the name.

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 14 parameters and complex document relationships, a one-sentence description is completely inadequate. It doesn't explain the item position's role in documents, required fields, or how to structure the request.

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 contains no parameter details. The schema covers 64% of parameters, but the description fails to compensate for the missing fields, leaving users to infer semantics from field names alone.

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

Purpose2/5

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

The description 'Create an item position' restates the tool name and title without adding any clarifying information. It does not explain what an item position is or how it differs from sibling tools like create_text_position or create_subposition.

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 usage guidance is provided. The description does not specify when to use this tool, what document types it applies to, or any alternatives.

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