Skip to main content
Glama
mydata-ag

bexio-mcp

Official
by mydata-ag

bexio Quotes

bexio_quotes
Destructive

Manage the complete quote lifecycle: create, send, accept, decline, and convert quotes to invoices or orders in bexio.

Instructions

Manage quotes/offers (bexio 2.0 kb_offer API). Status flow: 1 Draft -> 2 Pending (issued) -> 3 Confirmed / 4 Declined. Actions: "list" (all quotes; optional limit/offset/order_by — order_by one of id, total, total_net, total_gross, updated_at), "search" (search_criteria required, AND-combined; useful fields: id, kb_item_status_id, document_nr, title, contact_id, user_id, currency_id, total, is_valid_from, is_valid_until, updated_at), "get" (id), "create" (payload; typically contact_id, user_id, positions; document_nr only if automatic numbering is off), "update" (id + payload with fields to change), "delete" (id — permanently deletes the quote, cannot be undone), "issue" (id — moves a draft to pending and makes it visible to workflows), "revert_issue" (id — back to draft), "accept" (id), "decline" (id), "reissue" (id), "mark_as_sent" (id — flags as sent without emailing), "send" (id + email with recipient_email/subject/message, optional mark_as_open/attach_pdf; message must contain "[Network Link]"; emails the quote to the customer), "copy" (id + copy with contact_id required, optional contact_sub_id, is_valid_from, pr_project_id, title — returns the new quote), "pdf" (id; optional logopaper for letterhead and save_path to write the PDF to disk), "create_invoice" (id; optional positions to take over a subset — omit for all; returns the new invoice), "create_order" (id; optional positions — omit for all; returns the new order).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoQuote id (required for every action except "list", "search" and "create")
copyNoCopy parameters for "copy"
emailNoEmail parameters for "send"
limitNoMaximum number of results (default 500, max 2000)
actionYesOperation to perform
offsetNoNumber of results to skip (pagination)
payloadNoQuote fields for "create"/"update"
order_byNoField to order by; append "_desc" for descending (e.g. "id_desc")
logopaperNoFor "pdf": render the PDF on the letterhead paper
positionsNoFor "create_invoice"/"create_order": source positions to take over; omit to take all
save_pathNoFor "pdf": write the PDF to this file path instead of returning base64 inline
search_criteriaNoSearch conditions, combined with logical AND
Behavior5/5

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

Adds significant context beyond annotations: discloses that 'delete' is permanent, 'send' sends an email, 'pdf' can write to disk, and notes limitations like trial period email restriction. Also explains that 'viewed_by_client_at' is normally set by bexio. No contradiction with 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?

Well-organized with a status flow overview followed by action bullet points. While lengthy (17 actions), each sentence is informative and the structure is clear. No fluff, but could be slightly more streamlined.

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?

For a complex tool with 17 actions and nested parameters, the description covers all necessary context: status flow, action-specific requirements, parameter constraints, and edge cases. No output schema exists, but return values are implied by actions.

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%, but description adds value: lists useful search fields, explains position variants and max count, clarifies document_nr logic, and describes edge cases like 'viewed_by_client_at' writability.

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?

Description clearly states 'Manage quotes/offers' and lists 17 distinct actions, each with a specific verb-resource combination. The resource is unambiguously quotes, distinguishing it from sibling tools like invoices or orders.

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?

Detailed guidance for each action, including prerequisites (e.g., document_nr only when automatic numbering is off) and constraints (e.g., message must contain '[Network Link]'). However, it does not explicitly contrast with alternatives like bexio_invoices, though the tool name and sibling list make the distinction clear.

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