Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-bexio

by AIWerk

list_expenses

Read-onlyIdempotent

Retrieve expense records from Bexio with filters for date ranges, amounts, vendor, title, and more. Find specific expenses quickly by applying multiple search criteria.

Instructions

Get Expenses

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNocurrent page
sortNofield to sort by
limitNoresults per page
orderNosorting order
titleNofilter for Expense 'title', text containing in field
vendorNofilter for Expense 'vendor', text containing in fields lastname_company and firstname_suffix
net_maxNofilter for Expense 'net', the greatest accepted value
net_minNofilter for Expense 'net', the lowest accepted value
gross_maxNofilter for Expense 'gross', the greatest accepted value
gross_minNofilter for Expense 'gross', the lowest accepted value
project_idNofilter for Expense 'project_id'
document_noNofilter for Expense 'document_no', text containing in field
paid_on_endNofilter for Expense 'paid_on', the latest accepted date
supplier_idNofilter for Expense 'supplier_id'
currency_codeNofilter for Expense 'currency_code', text containing in field
paid_on_startNofilter for Expense 'paid_on', the earliest accepted date
created_at_endNofilter for Expense 'created_at', the latest accepted date
created_at_startNofilter for Expense 'created_at', the earliest accepted date
Behavior2/5

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

Annotations declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, which already disclose the safety profile. However, the description adds no behavioral context beyond the bare 'Get' – no mention of pagination, result structure, availability of filters, or any operational quirks. With annotations present, the bar is lower, but the description contributes nothing; hence a below-average score.

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 it is under-specification rather than efficient communication. It fails to earn its place by providing any useful information beyond the tool name. For a tool with 18 parameters and no output schema, this is inappropriately sparse.

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

Completeness1/5

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

With 18 parameters, no output schema, and a wide array of sibling tools, the description is severely incomplete. It does not explain return value shape, pagination semantics, date handling, or any filtering capabilities. The annotations mitigate some safety concerns, but the description alone leaves the agent with almost no operational understanding.

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?

The input schema covers 100% of the 18 parameters with per-field descriptions. The description itself does not explain any parameters, but it is not required to do so given the thorough schema. Baseline of 3 is appropriate because the schema carries the full semantic load.

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

Purpose2/5

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

The description 'Get Expenses' is essentially a synonym for the tool name (list_expenses) and title (List Expenses). It conveys the basic action and resource but offers no distinguishing scope (e.g., paginated list, all expenses) and does not differentiate it from numerous other list_* tools. This is a near-tautology, lacking specific verb+resource detail beyond the name.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus alternatives. No mention of filters, sorting, or related tools like search_expenses (if it exists). The description provides zero context for selecting this tool, forcing the agent to rely solely on the tool name.

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