Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-bexio

by AIWerk

list_bills

Read-onlyIdempotent

Retrieve bills from Bexio with filters for status, vendor, date, amount, and more. Find specific bills by search term or field values to manage accounting efficiently.

Instructions

Get Bills

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNocurrent page
sortNofield to sort by
limitNoLimit the number of results (max is 500)
orderNosorting order
titleNofilter for Bill 'title', text containing in field
statusNofilter for Bill 'status' (DRAFTS: [DRAFT], TODO: [BOOKED, PARTIALLY_CREATED, CREATED, PARTIALLY_SENT, SENT, PARTIALLY_DOWNLOADED, DOWNLOADED, PARTIALLY_PAID, PARTIALLY_FAILED, FAILED], PAID: [PAID], OVERDUE: [BOOKED, PARTIALLY_CREATED, CREATED, PARTIALLY_SENT, SENT, PARTIALLY_DOWNLOADED, DOWNLOADED,
vendorNofilter for Bill 'vendor', text containing in fields lastname_company and firstname_suffix
net_maxNofilter for Bill 'net', the greatest accepted value
net_minNofilter for Bill 'net', the lowest accepted value
fields[]Nofields for which search will be run (if no 'fields[]' is specified than searching will be done for all allowed fields)
gross_maxNofilter for Bill 'gross', the greatest accepted value
gross_minNofilter for Bill 'gross', the lowest accepted value
vendor_refNofilter for Bill 'vendor_ref', text containing in field
document_noNofilter for Bill 'document_no', text containing in field
search_termNoterm for which application will look for (minimum 3 signs, maximum 255 signs)
supplier_idNofilter for Bill 'supplier_id'
due_date_endNofilter for Bill 'due_date', the latest accepted date
bill_date_endNofilter for Bill 'bill_date', the latest accepted date
currency_codeNofilter for Bill 'currency_code', text containing in field
due_date_startNofilter for Bill 'due_date', the earliest accepted date
bill_date_startNofilter for Bill 'bill_date', the earliest accepted date
pending_amount_maxNofilter for Bill 'pending_amount', the greatest accepted value
pending_amount_minNofilter for Bill 'pending_amount', the lowest accepted value
average_exchange_rate_enabledNoindicates whether 'average_exchange_rate_enabled' is enabled, or not
Behavior2/5

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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds no further behavioral context, such as pagination behavior, default return of all bills, or the effect of filter parameters, which would be valuable for a list operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The description is only two words, which is extremely concise but under-specified for a tool with 24 parameters. It lacks any structural elements or additional context; this is under-specification rather than good conciseness.

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

Completeness2/5

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

Despite the rich schema and safety annotations, the description fails to mention that this is a list endpoint with pagination and filters. With no output schema, the description should clarify the return type and typical usage, making the current two-word description inadequate for such a complex tool.

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

Parameters3/5

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

With 100% schema description coverage, all 24 parameters have detailed descriptions. The tool description itself does not add any parameter semantics, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get Bills' uses a specific verb and resource, clearly indicating it retrieves bill data. It distinguishes from the sibling get_bill (singular) through the plural form, but lacks detail about the list/pagination nature or filtering capabilities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like get_bill or other list_ endpoints. No context is given about typical use cases or exclusions.

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/AIWerk/mcp-server-bexio'

If you have feedback or need assistance with the MCP directory API, please join our Discord server