Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-bexio

by AIWerk

update_payment

Idempotent

Update an existing payment in Bexio: change amount, currency, recipient, execution date, or other details. Correct or adjust payment information as needed.

Instructions

Update a payment

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountNoThe amount (decimal number) to send in the chosen currency. The amount may be exchanged by the bank if a currency is different from the currency of an account
messageNoMultiline description of the payment
currencyNoCurrency in which send a payment, according to ISO 4217
allowanceNoFor payments to other countries or with different currencies
is_salaryNoIf it is a salary payment
recipientNo
payment_idYes
execution_dateNoDate according to ISO 8601. Execution date of a payment (when the payment should be carried out by the bank), should be at least the next working day
qr_reference_nrNoA QR reference number or creditor reference number.
is_editing_restrictedNoIf set to true, editing will be restricted to the api client id which created the payment
additional_informationNoAdditional information on the payment slip
Behavior2/5

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

The annotations already indicate this is a non-read-only, idempotent, non-destructive operation. The description adds no extra behavioral context, such as whether payments in certain states are editable, permission requirements, or side effects. It simply restates the action without augmenting the annotation information.

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

Conciseness3/5

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

The description is a single, concise sentence with no wasted words. However, it is minimal to the point of being almost vague; it conveys only the basic verb+resource and omits useful details. It is appropriately sized but under-specified for a tool with 11 parameters.

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

Completeness2/5

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

This tool has a complex input schema (11 parameters, nested object) and no output schema. The description does not explain what happens on success, error conditions, or any special update constraints. It is insufficient for an agent to fully understand the tool's behavior or expected outcomes.

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

Parameters3/5

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

Schema description coverage is high (82%), with most parameters having detailed descriptions. The tool description provides no additional parameter meaning beyond what the schema already offers, so the baseline score of 3 applies.

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 'Update a payment' uses a specific verb and resource, clearly indicating the action of modifying an existing payment. It is distinct from siblings like 'update_outgoing_payment' and 'create_payment', though it does not elaborate on the scope or fields involved.

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 provided on when to use this tool versus alternatives such as 'create_payment', 'update_outgoing_payment', or 'cancel_payment'. The description does not mention any prerequisites or context that would help an agent choose this tool.

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