Skip to main content
Glama
mydata-ag

bexio-mcp

Official
by mydata-ag

bexio Purchase Orders

bexio_purchase_orders
Destructive

List, get, create, update, and delete purchase orders. Supports positions, taxes, and document details via the bexio 3.0 API.

Instructions

Manage purchase orders (bexio 3.0 API; numeric ids). Status (kb_item_status_id) is read-only: 22 Draft, 23 Open, 24 Partly, 25 Done, 26 Canceled. Actions: "list" (optional limit/offset and order_by: id, total, total_net, total_gross or updated_at; append "_desc" for descending), "get" (purchase order by numeric id), "create" (payload; all fields optional but typically contact_id, user_id and positions grouped as required/optional/discount arrays), "update" (id + payload of fields to change; positions are create-only — the update endpoint does not accept them and they are not sent), "delete" (id; permanently deletes the purchase order — cannot be undone).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoPurchase order id (required for get/update/delete)
limitNoMaximum number of results (default 500, max 2000)
actionYesOperation to perform
offsetNoNumber of results to skip (pagination)
payloadNoPurchase order fields (bexio 3.0 API; all fields optional — bexio applies defaults). Typically set at least contact_id, user_id and positions on create.
order_byNoField to order by; append "_desc" for descending (e.g. "id_desc")
Behavior5/5

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

Describes read-only status field, destructive deletion ('permanently deletes — cannot be undone'), and that update does not accept positions, adding context beyond annotations. Annotations include destructiveHint: true, consistent with the description. No contradiction.

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?

The description is informative but somewhat lengthy. However, it is front-loaded with core info (API, status, actions) and each sentence adds value. Minor redundancy (e.g., 'positions are create-only' mentioned twice). Still, overall structure is effective.

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 complexity (6 params, nested payload, no output schema), the description covers actions, parameters, and constraints thoroughly. However, it does not describe the return value format (e.g., a purchase order object) which would be helpful since no output schema exists. Otherwise, it is comprehensive.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds significant value: clarifies order_by fields and '_desc' suffix, notes payload fields typically required, explains status values (22 Draft, etc.), and specifies that positions are create-only. The description goes well beyond the schema descriptions.

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 it manages purchase orders, specifies the API version (bexio 3.0), numeric ids, and enumerates all five actions (list, get, create, update, delete) with distinct details, distinguishing it from siblings like bexio_invoices or bexio_orders.

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?

Each action is explicitly described with its required parameters (e.g., get requires id, list uses limit/offset). Constraints like status being read-only, positions not accepted in update are noted. However, no explicit guidance on when to prefer this tool over siblings (e.g., bexio_orders for sales orders, bexio_invoices for invoices).

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