Skip to main content
Glama
mydata-ag

bexio-mcp

Official
by mydata-ag

bexio Accounting

bexio_accounting
Destructive

Manage bexio accounting data: chart of accounts, account groups, calendar years, VAT periods, taxes, and journal entries using list, search, create, and delete actions.

Instructions

Access the bexio accounting foundation: chart of accounts, account groups, calendar/business years, VAT periods, taxes and the accounting journal. Select a "resource" and an "action". Valid combinations: accounts: "list", "search" (search_criteria required; searchable fields: account_no, name, account_type, fibu_account_group_id); account_groups: "list"; calendar_years: "list", "search" (searchable fields: start, end, is_vat_subject, vat_accounting_method, vat_accounting_type), "get" (id), "create" (payload; useful fields: year, is_vat_subject, is_annual_reporting, vat_accounting_method, vat_accounting_type, default_tax_income_id, default_tax_expense_id — creating a future year generates all years in between and returns them as an array); business_years: "list", "get" (id); vat_periods: "list", "get" (id); taxes: "list" (optional filters scope=active|inactive, date=validity date, types=sales_tax|pre_tax), "get" (id), "delete" (id — permanently deletes the tax, cannot be undone); journal: "list" (optional from/to date range and account_uuid filters; requires the "accounting" API scope). All "list" and "search" actions accept limit/offset pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoResource id (required for "get" and "delete")
toNojournal only: include entries until this ISO 8601 date
dateNotaxes list only: show taxes active at this ISO 8601 date
fromNojournal only: include entries on/after this ISO 8601 date
limitNoMaximum number of results (default 500, max 2000)
scopeNotaxes list only: filter active or inactive taxes
typesNotaxes list only: filter by tax type
actionYesOperation to perform (see description for valid resource/action combinations)
offsetNoNumber of results to skip (pagination)
payloadNoCalendar year fields for "create". All fields are optional per the API schema.
resourceYesAccounting resource to operate on
account_uuidNojournal only: only entries of the account with this uuid
search_criteriaNoSearch conditions, combined with logical AND
Behavior4/5

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

Annotations indicate destructiveHint=true, and the description elaborates on destructive actions (e.g., tax delete is permanent) and non-destructive ones. Also mentions API scope requirements for journal. No contradictions with annotations.

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?

Description is front-loaded with purpose and then enumerates combinations efficiently. While detailed, each sentence adds value. Could be slightly more concise but well-organized.

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 the tool's complexity (13 parameters, nested objects, multiple resources), the description covers most aspects including pagination, optional filters, and return behavior for create. No output schema exists, but the description compensates with behavioral notes.

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?

Schema coverage is 100%, but description adds value by explaining searchable fields for accounts and calendar_years, the effect of creating a future calendar year, and the meaning of payload fields. This goes beyond the schema definitions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: accessing the bexio accounting foundation with specific sub-resources. It lists all valid resource/action combinations, distinguishing it from sibling tools like bexio_invoices or bexio_contacts.

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?

Provides explicit instructions for each resource and action, including required parameters like search_criteria for search actions and optional filters for taxes and journal. Lacks explicit when-not-to-use guidance but is otherwise clear.

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