Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-bexio

by AIWerk

create_project

Creates a new project in Bexio by setting its name, type, status, and associated contact and user.

Instructions

Create project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
commentNo
user_idYesReferences a [user object](#operation/v3ListUsers)
end_dateNo
contact_idYesReferences a [contact object](#operation/v2ListContacts)
start_dateNo
document_nrNoCan not be used if “automatic numbering” is activated in frontend-settings. Required if “automatic numbering” deactivated. https://help.bexio.com/s/article/000001721
pr_state_idYesReferences a [project status object](#operation/v2ListProjectStatus)
contact_sub_idNoReferences a [contact object](#operation/v2ListContacts)
pr_budget_type_idNoThe following budget types are available: | Id | Name | Description | | ------ | ------ | ------ | | 1 | type_budgeted_costs | Total budget costs | | 2 | type_budgeted_hours | Total budget hours | | 3 | type_service_budget | Budget for each client services | | 4 | type_service_employees | Budget for
pr_invoice_type_idNoThe following invoice types are available: | Id | Name | Description | | ------ | ------ | ------ | | 1 | type_hourly_rate_service | Hourly rate for client services | | 2 | type_hourly_rate_employee | Hourly rate for employee | | 3 | type_hourly_rate_project | Hourly rate for project | | 4 | type_fi
pr_project_type_idYesReferences a [project type object](#operation/v2ListProjectType)
pr_budget_type_amountNoThis field can only be edited if the `pr_budget_type` is set. (Only supported for budget types: `type_budgeted_costs` and `type_budgeted_hours`)
pr_invoice_type_amountNoThis field can only be edited if the `pr_invoice_type` is set. (Only supported for invoice types: `type_hourly_rate_project` and `type_fix`)
Behavior2/5

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

The description adds no behavioral transparency beyond the annotations. Annotations indicate a non-read-only, non-destructive write operation, but the description does not explain side effects, required permissions, or what kind of data is created. It simply labels the action.

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 only two words, which is not a waste of words but is under-specified. It lacks the necessary detail to be considered appropriately sized for a tool with 14 parameters and no output schema.

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 (14 parameters, 5 required, no output schema), the description is highly inadequate. It does not mention return values, required fields, or any operational context, leaving the agent with almost no guidance beyond the schema itself.

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 provides descriptions for about 71% of parameters, but the description itself offers no parameter information. It does not compensate for the undocumented required 'name' and other fields, leaving a gap that the description could have filled.

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

Purpose3/5

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

The description 'Create project' clearly states the action and resource, but it essentially restates the tool name without adding any specific context or distinguishing details. It does not differentiate from sibling tools like update_project or create_milestone beyond the name itself.

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. The description provides no context about prerequisites, related tools, or typical use cases, leaving the agent to infer usage solely from the tool name.

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