Skip to main content
Glama
mydata-ag

bexio-mcp

Official
by mydata-ag

bexio Timesheets

bexio_timesheets
Destructive

Create, read, update, and delete timesheets in bexio. Track time by duration or start/end range, search entries by user or project, and list statuses.

Instructions

Manage timesheets (time tracking entries) in bexio. Actions: "list" (all timesheets, optional limit/offset/order_by; order_by supports id, date), "search" (search_criteria required; searchable fields: id, client_service_id, contact_id, user_id, pr_project_id, status_id), "get" (timesheet by numeric id), "create" (payload required: user_id, client_service_id, allowable_bill, tracking; tracking is either { type: "duration", date, duration } or { type: "range", start, end }), "update" (id + payload of fields to change), "delete" (permanently delete a timesheet by id — cannot be undone), "list_statuses" (all timesheet statuses, e.g. "In Progress"; optional limit/offset/order_by with id, name). Read timesheets may also contain a tracking of type "stopwatch" (created via the bexio UI).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoTimesheet id (required for get/update/delete)
limitNoMaximum number of results (default 500, max 2000)
actionYesOperation to perform
offsetNoNumber of results to skip (pagination)
payloadNoTimesheet fields. Required on create: user_id, client_service_id, allowable_bill, tracking.
order_byNoField to order by; append "_desc" for descending (e.g. "id_desc")
search_criteriaNoSearch conditions, combined with logical AND
Behavior4/5

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

Description adds behavioral context beyond annotations: delete is 'permanently delete ... cannot be undone', and read timesheets may contain 'stopwatch' tracking from UI. Annotations already signal destructiveHint=true, so the description reinforces and adds detail. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is densely packed with information in a well-organized list format, front-loading the overall purpose. Every sentence is necessary and informative, with no wasted words.

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?

Despite lacking an output schema, the description covers all main actions and their constraints (required fields, pagination via limit/offset, order_by syntax, search criteria operators). It does not describe return values explicitly, but for a management tool with multiple actions, this is sufficient.

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 description coverage, baseline is 3. The description adds value by specifying searchable fields, required payload fields for create, and the tracking object's two variants (duration vs range) with examples. This supplements the schema's property descriptions.

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 it manages timesheets (time tracking entries) in bexio and enumerates all supported actions (list, search, get, create, update, delete, list_statuses). This specific verb-resource pairing distinguishes it clearly from sibling tools like bexio_projects or bexio_tasks.

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 explicit context for each action: e.g., 'list' returns all timesheets, 'search' requires search_criteria with specified searchable fields, 'create' requires certain payload fields. However, it does not compare this tool to siblings or state when not to use it, which is a minor gap.

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