Skip to main content
Glama
mydata-ag

bexio-mcp

Official
by mydata-ag

bexio Document Positions

bexio_document_positions
Destructive

Create, read, update, and delete line-item positions on quotes, orders, and invoices. Supports custom items, articles, text blocks, subtotals, discounts, page breaks, and subpositions.

Instructions

Manage line-item positions on sales documents (quotes/kb_offer, orders/kb_order, invoices/kb_invoice). position_type selects the kind of position: "custom" (free position: amount, unit_id, account_id, tax_id, text, unit_price, discount_in_percent), "article" (item position: same fields plus article_id referencing an item), "text" (text block: text, show_pos_nr), "subtotal" (text), "discount" (text, is_percentual, value), "pagebreak" (pagebreak flag) and "subposition" (grouping position: text, show_pos_nr). Actions: "list" (all positions of that kind on the document; optional limit/offset), "get" (single position, requires position_id), "create" (payload with the fields of the chosen position_type), "update" (requires position_id + payload; partial updates allowed), "delete" (requires position_id — permanently removes the position, cannot be undone). All actions require document_type, document_id and position_type. is_optional is writable only on custom/article positions and only honored on quotes and orders. Amounts/prices are strings with max. 6 decimals.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results for "list" (max 2000)
actionYesOperation to perform
offsetNoResults to skip for "list"
payloadNoPosition fields (all optional; only the fields of the selected position_type apply). custom: amount, unit_id, account_id, tax_id, text, unit_price, discount_in_percent, is_optional. article: same as custom plus article_id. text: text, show_pos_nr. subtotal: text. discount: text, is_percentual, value. pagebreak: pagebreak. subposition: text, show_pos_nr.
document_idYesId of the parent document (quote, order or invoice)
position_idNoPosition id (required for get/update/delete)
document_typeYesType of the parent document: kb_offer (quote), kb_order (order) or kb_invoice (invoice)
position_typeYesKind of position; maps to the kb_position_custom/kb_position_article/kb_position_text/kb_position_subtotal/kb_position_discount/kb_position_pagebreak/kb_position_subposition endpoints
Behavior4/5

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

Discloses that delete is permanent and irreversible, consistent with destructiveHint annotation. Adds details on field applicability and value format (max 6 decimals). No contradictions with annotations.

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

Conciseness4/5

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

Description is dense but well-organized: first sentence defines scope, then enumerates position types and their fields, then actions, then additional notes. It efficiently packs information without redundancy, though length is justified by complexity.

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

Completeness4/5

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

Given the tool's complexity (8 params, 7 position types, 5 actions), the description covers most aspects: actions, field mappings, constraints, and pagination. No output schema, but missing return structure is acceptable for a CRUD tool. Slight gap: no response example.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. Description adds value by mapping fields to each position_type, explaining special behaviors (is_optional, is_percentual), and providing format constraints (max 6 decimals). This goes beyond the schema alone.

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?

Clearly states 'Manage line-item positions on sales documents' and enumerates specific document types and position types. Distinguishes itself from sibling tools by focusing on document positions.

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

Usage Guidelines4/5

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

Explains each action (list, get, create, update, delete) and required parameters. Provides context on which fields apply to which position_type and notes limitations like is_optional only on quotes/orders. Does not explicitly state when not to use but offers sufficient guidance.

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/mydata-ag/bexio-mcp'

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