Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-bexio

by AIWerk

create_payment

Create a payment in Bexio by specifying recipient, amount, currency, execution date, and type (IBAN or QR).

Instructions

Create a payment

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesType of the payment. Each payment requires different fields
amountYesThe 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
currencyYesCurrency in which send a payment, according to ISO 4217
allowanceNoFor payments to other countries or with different currencies
is_salaryYesIf it is a salary payment
recipientYes
account_idYes
execution_dateYesDate 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.
purchase_referenceNo
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 a write operation (readOnlyHint=false), but the description adds no behavioral context beyond the generic 'create.' It provides no information about side effects, permissions, or return behavior, which is especially important for a complex payment creation tool.

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 three-word description is under-specified rather than concise. It contains no information that could not be inferred from the tool name, so it fails to earn its place. Effective conciseness would preserve useful guidance without verbosity.

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?

This is a complex tool with 13 parameters, nested objects, and type-specific payment variants, yet the description provides no context. It does not explain the difference between payment types, which fields are conditional, or how this tool relates to sibling payment creation tools. The description is severely inadequate.

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

Parameters2/5

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

The schema covers 77% of parameters with descriptions, but the tool description contributes nothing to parameter understanding. It does not highlight the critical type-dependent fields, such as 'type' or 'qr_reference_nr', nor explain their relationships. The description adds zero value beyond the schema.

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 'Create a payment' is a direct restatement of the tool's name and adds no distinguishing information. It fails to differentiate from sibling tools like create_outgoing_payment or create_invoice_payment, making it tautological rather than clarifying.

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?

There is no guidance on when to use this tool or when to prefer an alternative. It does not mention required fields, payment type differences (iban vs qr), or any context that would help an agent decide to invoke 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