Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-bexio

by AIWerk

create_calendar_year

Create a Bexio calendar year with VAT subject, accounting type/method, annual reporting, and default tax IDs for income and expense.

Instructions

Create calendar year.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNoThe year for which we want to create an entry. It is possible to create years 10 years ahead and higher than 2016 year. If it is a future year, we generate all in between with the settings the user has chosen.
is_vat_subjectNoDetermines if the calendar year is vat subjected or not.
is_annual_reportingNoDetermines if the calendar year has annual reporting enabled.
vat_accounting_typeNoVat accounting type.
default_tax_income_idNoDetermine default tax ID for income. References a [tax object](#operation/ListTaxes)
vat_accounting_methodNoVat accounting method.
default_tax_expense_idNoDetermine default tax ID for expense. Tax ID is not required if the client has the plan bexio mini. In this case, the year is created with the tax ID from the previous year. References a [tax object](#operation/ListTaxes).
Behavior2/5

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

The description provides no behavioral information beyond what the name implies. Annotations indicate readOnlyHint=false and idempotentHint=false, but the description does not mention important behaviors such as auto-generating intermediate future years or relying on previous year's tax ID, which are only found in the schema.

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 brief—a single sentence that essentially restates the tool's name. It is under-specified for a tool with 7 parameters and lacks any additional structure or context that would earn its place.

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?

Given the tool's complexity (7 parameters, no output schema), the one-line description is inadequate. It omits return values, side effects, prerequisites, and the auto-generation behavior for future years, leaving the agent under-informed.

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?

The schema description coverage is 100%, so the schema already fully documents all 7 parameters. The description adds no parameter-level information, but the baseline score of 3 applies because the schema carries the heavy lifting.

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 the verb 'create' and the resource 'calendar year', distinguishing it from sibling tools like get_calendar_year or list_calendar_years. However, it does not add any extra scope or differentiate from create_business_year, which is also a sibling.

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 versus alternatives, no prerequisites, and no exclusions. The description simply repeats the tool's name without any contextual usage information.

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