Skip to main content
Glama
mydata-ag

bexio-mcp

Official
by mydata-ag

bexio Master Data

bexio_master_data
Destructive

Manage master data resources like countries, titles, and languages with list, search, create, update, and delete operations. Supports filtering, pagination, and ordering for efficient data handling.

Instructions

Manage small bexio master-data lookup resources. Choose a "resource" and an "action". Resources and their supported actions: salutations, titles, units — list, search, get, create, update, delete (payload: {name}); countries — list, search, get, create, update, delete (payload: {name, name_short, iso3166_alpha2}); languages, payment_types, communication_types — list, search only (read-only); business_activities — list, search, create (payload: {name, default_is_billable?, default_price_per_hour?, account_id?}). Actions: "list" (optional limit/offset; order_by fields "id"/"name" for titles, countries, languages, payment_types, business_activities and communication_types — countries and payment_types also "name_short"; salutations and units do not support order_by), "search" (search_criteria required; searchable fields: "name" everywhere, countries also "name_short"/"iso3166_alpha2", languages also "iso_639_1"), "get" (id required), "create" (payload required; see per-resource shapes above), "update" (id + payload of fields to change), "delete" (id required — permanently deletes the entry, cannot be undone).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoEntry id (required for get/update/delete)
limitNoMaximum number of results (default 500, max 2000)
actionYesOperation to perform (not every resource supports every action; see description)
offsetNoNumber of results to skip (pagination)
payloadNoEntry fields. Required on create: name (all resources); countries additionally require name_short and iso3166_alpha2. Business activities may also set default_is_billable, default_price_per_hour, account_id.
order_byNoField to order by; append "_desc" for descending (e.g. "id_desc")
resourceYesMaster-data resource to operate on
search_criteriaNoSearch conditions, combined with logical AND
Behavior4/5

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

Discloses that delete is permanent ('cannot be undone'), matches annotations (destructiveHint: true). Also notes read-only resources. Adds value beyond annotations by detailing ordering behavior and search constraints. No contradiction.

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?

Well-organized with bullet-like lists for resources and actions, but somewhat lengthy due to comprehensive detail. Front-loaded with purpose and resource overview. Nearly every sentence adds value, though could be slightly trimmed.

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 (8 parameters, nested objects, no output schema), the description covers all necessary aspects: action rules, payload shapes, search criteria, ordering, pagination. Complete enough for an AI to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds substantial extra meaning: per-resource payload shapes, which fields are required on create, which resources support order_by and which fields, searchable fields per resource. Greatly enhances parameter understanding.

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?

Clearly states the tool manages 'small bexio master-data lookup resources' and lists all resources and actions. Distinguishes from sibling tools by focusing on master data rather than accounting, contacts, invoices, etc.

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 detailed guidance on which resources support which actions (e.g., 'languages, payment_types, communication_types — list, search only'), explains ordering options per resource, and searchable fields. Lacks explicit when-not-to-use or alternatives but the context is clear from the resource list.

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