Skip to main content
Glama
mydata-ag

bexio-mcp

Official
by mydata-ag

bexio Users

bexio_users
Destructive

Retrieve and manage bexio users, including read-only access to real users and full CRUD operations for fictional users who appear in dropdowns but cannot log in.

Instructions

Read bexio users and manage fictional users (fictional users appear in dropdowns but cannot log in). Actions: "list" (all users, optional limit/offset), "get" (user by id), "me" (the user authenticated by the current token), "list_fictional" (all fictional users, optional limit/offset), "get_fictional" (fictional user by id), "create_fictional" (payload required: salutation_type, firstname, lastname, email; optional title_id), "update_fictional" (id + payload of fields to change), "delete_fictional" (permanently delete a fictional user by id — cannot be undone), "permissions" (activated components and the full permission map of the logged-in user). Regular users are read-only via the API; only fictional users can be created, updated or deleted. is_superadmin/is_accountant are only included when the authenticated user is a superadmin.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoUser id (required for "get") or fictional user id (required for get/update/delete_fictional)
limitNoMaximum number of results (default 500, max 2000)
actionYesOperation to perform
offsetNoNumber of results to skip (pagination)
payloadNoFictional user fields. Required on create: salutation_type, firstname, lastname, email.
Behavior4/5

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

Beyond the annotations (destructiveHint=true), the description warns that deletion cannot be undone and notes that certain fields (is_superadmin/is_accountant) are only returned for superadmins. It also explains that fictional users appear in dropdowns but cannot log in, adding valuable behavioral context.

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 well-structured with action names in quotes for easy scanning. It front-loads the main purpose and then enumerates actions. While slightly lengthy, it avoids redundancy and each sentence adds value.

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 (multiple actions, 5 parameters, no output schema), the description is fairly complete. It covers all actions, their requirements, pagination limits, and behavioral notes. It could detail return values for specific actions (e.g., what 'me' returns), but overall it provides sufficient context.

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, the baseline is 3. The description adds value by summarizing required payload fields for create_fictional (salutation_type, firstname, lastname, email) and clarifying that title_id is optional. It also explains the conditional inclusion of admin fields.

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 specifies all actions (list, get, me, list_fictional, get_fictional, create_fictional, update_fictional, delete_fictional, permissions) and distinguishes between regular users (read-only) and fictional users (CRUD). This specificity differentiates it from sibling tools like bexio_contacts or bexio_master_data.

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 context on when to use each action (e.g., regular users are read-only, fictional users can be modified) and mentions optional parameters for pagination. However, it does not explicitly state when not to use this tool versus alternatives or provide direct comparisons to sibling tools.

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