Skip to main content
Glama
mydata-ag

bexio-mcp

Official
by mydata-ag

bexio Contacts

bexio_contacts
Destructive

Manage contacts in the bexio central address book: list, search, create, update, delete, and restore contacts referenced by quotes, orders, invoices, and projects.

Instructions

Manage bexio contacts (companies and persons; the central address book referenced by quotes, orders, invoices, projects). Actions: "list" (all contacts; optional limit/offset/order_by [id|nr|name_1|updated_at, append "_desc"], show_archived), "search" (search_criteria required; useful searchable fields: id, nr, name_1, name_2, mail, postcode, city, country_id, contact_type_id, contact_group_ids, user_id, updated_at; optional list params and show_archived), "get" (contact by id; optional show_archived; includes base64 profile_image), "create" (payload required: contact_type_id [1=company, 2=person], name_1, user_id, owner_id), "update" (id + payload of fields to change), "delete" (permanently deletes the contact — cannot be undone; a deleted contact can only be restored shortly afterwards via the restore action), "bulk_create" (contacts array of contact payloads, same required fields as create), "restore" (restore a deleted contact by id).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoContact id (required for get/update/delete/restore)
limitNoMaximum number of results (default 500, max 2000)
actionYesOperation to perform
offsetNoNumber of results to skip (pagination)
payloadNoContact fields. Required on create/bulk_create: contact_type_id, name_1, user_id, owner_id. Note: the API spec also marks these four fields as required on update (v2EditContact), though partial edits generally work. The legacy combined "address" field is deprecated (read-only); use street_name/house_number/address_addition.
contactsNoContact payloads for "bulk_create"
order_byNoField to order by; append "_desc" for descending (e.g. "id_desc")
show_archivedNoShow archived elements only (list/search/get)
search_criteriaNoSearch conditions, combined with logical AND
Behavior4/5

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

The description adds context beyond annotations by noting that delete permanently removes contacts (cannot be undone) but can be restored shortly afterward, and that get includes base64 profile_image. Annotations already indicate destructiveHint true, so the description enhances transparency.

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, listing each action with its parameters and constraints. It is somewhat lengthy but organized, making it easy to scan. Every sentence adds information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of the tool (multiple actions, nested objects, search criteria), the description covers all essential aspects: actions, required fields, searchable fields, deletion behavior, pagination, and deprecation notes. It leaves no major gaps.

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 descriptions already document parameters. The tool description adds value by explaining searchable fields, required fields for create/bulk_create, and deprecation of the address field, which aids effective parameter use.

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 manages bexio contacts, identifies it as the central address book referenced by quotes, orders, invoices, and projects, and lists all supported actions (list, search, get, create, update, delete, bulk_create, restore). This specificity distinguishes it from sibling tools.

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 implies usage for contact management and highlights that it is the central address book, providing context. However, it does not explicitly state when to use this tool versus alternatives or when not to use certain actions.

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