Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-bexio

by AIWerk

create_bill

Create a new bill in Bexio by specifying supplier, contact partner, dates, line items, amounts, discounts, and optional payment details.

Instructions

Create new Bill

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNo
addressYesAddress
paymentNo
due_dateYes
item_netYesIndicates whether 'amount' in 'line_items' is net or gross.
bill_dateYes
discountsYes
amount_manNoRequired when 'manual_amount' is true. Maximum of 17 digits and maximum of 2 decimal digits.
line_itemsYes
vendor_refNo
amount_calcNoRequired when 'manual_amount' is false. Maximum of 17 digits and maximum of 2 decimal digits.
supplier_idYes
currency_codeYes
exchange_rateNoRequired when 'currency_code' is different from 'base_currency_code' (taken from settings). Maximum of 5 digits and maximum of 10 decimal digits.
manual_amountYesindicates whether 'amount_man' or 'amount_calc' is required and considered as bill amount
attachment_idsYes
purchase_order_idNo
contact_partner_idYes
qr_bill_informationNo
base_currency_amountNoRequired when 'currency_code' is different from 'base_currency_code' (taken from settings). Maximum of 17 digits and maximum of 2 decimal digits.
Behavior2/5

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

The description adds no behavioral context beyond the annotations. Annotations already indicate a non-read-only, non-destructive, non-idempotent operation, but the description doesn't explain side effects, required relationships, or any operational nuances.

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 brief, but this is under-specification rather than effective conciseness. It essentially restates the tool name without elaboration, offering no value beyond the schema.

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 complex tool with 20 parameters, 11 required fields, nested objects, and no output schema, the one-line description is grossly insufficient. It lacks context on the bill creation workflow, relationships between fields, and operational behavior.

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

Parameters1/5

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

The description contains no parameter information. With schema description coverage at only 35%, the description should compensate, but it fails to mention any of the 20 parameters, required fields, or the critical manual_amount vs amount_calc distinction.

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 uses a clear verb 'Create' and resource 'Bill', stating the core action. It distinguishes from sibling tools like create_invoice or create_purchase_order by naming the specific resource, though it provides no additional scoping or detail.

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 given on when to use this tool versus alternatives such as update_bill or create_purchase_order. There is no mention of prerequisites, workflows, or scenarios where creating a bill is appropriate.

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