Skip to main content
Glama
mydata-ag

bexio-mcp

Official
by mydata-ag

bexio Bank Payments

bexio_banking_payments
Destructive

Control outgoing bank payments: list, create, update, cancel, or delete payments with IBAN and QR support, filtering, and full lifecycle management.

Instructions

Manage outgoing bank payments (bexio banking 4.0 API). Actions: "list" (optional filter_by expression, page/per_page), "get" (payment by id/uuid), "create" (payload required: account_id, amount, currency, execution_date, is_salary, recipient, type), "update" (id + payload of fields to change; only open payments; account_id, type and purchase_reference cannot be changed), "cancel" (cancel a transmitted/downloaded payment by id — cannot be undone), "delete" (permanently delete a payment by id — cannot be undone). Payment ids are strings (uuid or numeric id).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoPayment id or uuid (required for get/update/cancel/delete)
pageNoPage number for "list"; the first page is 0 (API default)
actionYesOperation to perform
payloadNoPayment fields. Required on create: account_id, amount, currency, execution_date, is_salary, recipient, type. account_id, type and purchase_reference are create-only: the update endpoint does not accept them, so they cannot be changed and are ignored on "update".
per_pageNoResults per page for "list" (default 500, max 2000)
filter_byNoFilter expression for "list", e.g. "status_open"; ranges use "_", multiple filters use ";"
Behavior4/5

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

The description adds important behavioral details beyond annotations: cancel and delete cannot be undone, update has restrictions on mutable fields, create requires specific payload. This complements the destructiveHint and readOnlyHint annotations well.

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 moderately concise, organized by action in a single paragraph. It front-loads the purpose and then details each action. Could be improved with bullet points or clearer separation, but not overly verbose.

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 no output schema, the description provides reasonable context for each action's behavior and constraints. It mentions that payment ids are strings (uuid or numeric). However, it does not describe the response format for list/get, which might be needed for integration.

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

Parameters4/5

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

With 100% schema coverage, baseline is 3. The description adds value by explaining that certain fields (account_id, type, purchase_reference) are create-only and ignored on update, which is not in the schema descriptions. This helps agents avoid invalid update requests.

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 clearly states it manages outgoing bank payments with specific actions (list, get, create, update, cancel, delete). However, it does not explicitly differentiate from sibling tools like bexio_outgoing_payments, relying on the tool name and context.

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?

The description provides clear conditions for each action: update only open payments with certain immutable fields, cancel/delete are irreversible, create requires specific fields. It does not compare to alternative tools but within the tool it gives actionable guidance.

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