Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-bexio

by AIWerk

update_expens

Idempotent

Update an existing expense in Bexio by its ID. Modify payment date, currency, amount, or attachments to keep records accurate.

Instructions

Update Expense

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesid of Expense to update
titleNo
amountYesMaximum of 17 digits and maximum of 2 decimal digits.
tax_idNo
addressNoAddress
paid_onYes
document_noNo
supplier_idNo
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.
attachment_idsYesList of file ids that should be attached to this Expense. Cannot have duplicates.
bank_account_idNo
booking_account_idNo
base_currency_amountNoMaximum of 17 digits and maximum of 2 decimal digits.
Behavior2/5

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

Annotations already indicate readOnlyHint: false, destructiveHint: false, idempotentHint: true, and openWorldHint: true. The description adds no behavioral context beyond what the annotations supply. It does not mention that an existing expense ID is required, that updates are idempotent, or any side effects. No value beyond annotations is provided.

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 short, but this is under-specification rather than conciseness. A single uninformative phrase does not effectively convey the tool's purpose, parameters, or behavior. Every word should add value, but here the words add none.

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?

The tool has a complex schema with 14 parameters, nested objects, and no output schema. The description must explain return values, prerequisites, and operational context, but it does none of this. It is completely inadequate for an agent to invoke this tool correctly.

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?

With 14 parameters and only 43% schema description coverage, the description must compensate for the lack of parameter details. However, 'Update Expense' provides zero information about any parameter. The agent is left entirely to the schema, which has many properties with no description. This is a critical deficiency.

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 'Update Expense' is essentially a restatement of the tool name 'update_expens' with no additional detail. It fails to distinguish this tool from sibling tools like 'update_expense_booking' or 'create_expens', and provides no information about what an 'Expense' is or what updating entails.

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?

The description provides no guidance on when to use this tool versus alternatives. It mentions no prerequisites, no exclusions, and no alternative tools. An agent would have no idea whether to choose 'update_expens' over 'update_expense_booking' or other related operations.

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