Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-bexio

by AIWerk

list_currencies

Read-onlyIdempotent

Retrieve a list of currencies from Bexio, optionally with exchange rates valid on a given date. Use limit, offset, and embed parameters to customize the response.

Instructions

Fetch a list of currencies

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNothe validity date for the fetched exchange rate
embedNoThe embed parameters is being used for embedding related resources in the response. <br><br> **Example** <br> In case of ```embed=exchange_rate``` the fields ```exchange_rate```, ```exchange_rate_id```, ```ratio```, ```exchange_rate_to_ratio```, ```source```, ```source_reason``` and ```exchange_rate
limitNoLimit the number of results (max is 2000)
offsetNoSkip over a number of elements by specifying an offset value for the query
Behavior2/5

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

The description adds no behavioral context beyond what the annotations already declare (readOnlyHint, idempotentHint). It does not mention pagination via limit/offset, the date filtering parameter, or any response shape, leaving agents without additional insight into how the tool behaves.

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 a single, efficient sentence with no redundant words. It is appropriately terse, though this short length contributes to under-specification.

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?

With no output schema and a very terse description, agents have no indication of what the returned list contains, how optional parameters affect results, or what distinguishes this listing from similar sibling tools. The presence of four optional parameters makes this lack of context particularly limiting.

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?

Schema description coverage is 100%, so all parameters (date, embed, limit, offset) are already documented in the schema. The tool description adds no extra parameter semantics, which is acceptable given the high schema coverage, but no additional value is provided.

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 clearly states the action ('Fetch') and resource ('a list of currencies'), making the core purpose understandable. However, it does not differentiate this tool from sibling tools like list_currencies_codes or list_exchange_rates_for_currencies, which may lead to confusion.

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?

There is no guidance on when to use this tool versus the many currency-related siblings. No mention of alternatives, exclusions, or specific scenarios where this list is appropriate.

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