Skip to main content
Glama
mydata-ag

bexio-mcp

Official
by mydata-ag

bexio Files

bexio_files
Destructive

List, search, upload, download, preview, update, and delete files stored in bexio, including attachments.

Instructions

Manage files stored in bexio (uploads, attachments; 3.0 API). Actions: "list" (all files; optional archived_state, offset, order_by — order_by fields: id, created_at, source_id, uuid, name, size_in_bytes, comma-combinable with "_asc"/"_desc" suffix), "search" (search_criteria required; searchable fields: id, uuid, created_at, name, extension, size_in_bytes, mime_type, user_id, is_archived, source_id; optional archived_state, limit, offset), "get" (file metadata by id), "download" (file content by id; returns base64 or writes to optional save_path), "preview" (preview image of the file by id; returns base64 or writes to optional save_path), "usage" (where the file is attached: reference class, title, document number; by id), "upload" (create a new file from file_path on disk OR content_base64 + file_name; file_name overrides the file_path basename), "update" (id + payload: name, is_archived, source_type), "delete" (marks the file as deleted by id — cannot be undone).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoFile id (required for get/download/preview/usage/update/delete)
limitNoMaximum number of results for "search" (default 500, max 2000)
actionYesOperation to perform
offsetNoNumber of results to skip for "list"/"search"
payloadNoFile fields for "update"; send only the fields to change (PATCH semantics).
order_byNoSort order for "list": id, created_at, source_id, uuid, name or size_in_bytes; append "_asc"/"_desc" and combine multiple fields with a comma
file_nameNoFile name including extension (required for "upload" with content_base64; overrides the file_path basename)
file_pathNoPath of a local file to upload (for "upload")
save_pathNoFor "download"/"preview": write the file to this local path instead of returning base64 inline
archived_stateNoInclude/exclude archived files for "list" and "search"
content_base64NoBase64-encoded file content to upload (for "upload", alternative to file_path)
search_criteriaNoSearch conditions, combined with logical AND
Behavior4/5

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

Annotations set destructiveHint=true and the description reinforces that delete 'cannot be undone'. It discloses upload alternatives (file_path or content_base64 + file_name), and download/preview return base64 or write to save_path. While no rate limits or auth details are given, the key behavioral traits are covered beyond annotations.

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 dense but well-organized with a general statement followed by per-action details in quotes. It front-loads the action list and uses concise language. While long, every sentence adds value, and the structure aids scanning.

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 12 parameters and nested objects, the description covers all actions' required inputs (e.g., id for get/download/preview/usage/update/delete) and upload alternatives. It explains search criteria format and archived_state options. The lack of output schema is acceptable as operations are clear. Slightly more detail on pagination or error handling would raise the score.

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?

Schema coverage is 100%, so baseline is 3. The description adds value by explaining which parameters belong to which actions (e.g., order_by only for list, search_criteria for search), listing searchable fields, and noting that file_name overrides basename for upload. This goes beyond just listing parameter types.

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 files stored in bexio, enumerates all actions (list, search, get, download, preview, usage, upload, update, delete), and distinguishes itself from sibling tools by focusing on file operations.

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 lists required and optional parameters per action (e.g., id for get/download/preview, search_criteria for search). It explains when to use list vs search (list returns all files, search filters with criteria). However, it does not explicitly exclude non-file tasks or compare with alternative tools, but sibling tool names indicate clear domain separation.

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