Skip to main content
Glama
berthelius

Frihet MCP Server

List Invoices

list_invoices
Read-onlyIdempotent

Fetch a paginated list of invoices filtered by status and date range, sorted newest first.

Instructions

List all invoices with optional pagination and filters. Returns a paginated list sorted by issue date (newest first). Supports filtering by status (draft/sent/paid/overdue/cancelled) and date range. Example: status='paid', from='2026-01-01', to='2026-03-31', limit=20 / Lista facturas con paginacion y filtros opcionales. Soporta filtrado por estado y rango de fechas.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoEnd date filter in ISO 8601 (YYYY-MM-DD) / Fecha fin
fromNoStart date filter in ISO 8601 (YYYY-MM-DD) / Fecha inicio
afterNoCursor for cursor-based pagination (document ID) / Cursor para paginacion basada en cursor
limitNoMax results per page (1-100, default 50) / Resultados por pagina
fieldsNoComma-separated field names to return (e.g. 'id,clientName,total') / Campos a devolver
offsetNoNumber of results to skip / Resultados a saltar
statusNoFilter by invoice status / Filtrar por estado
clientIdNoFilter by client ID / Filtrar por ID de cliente
seriesIdNoFilter by invoice series ID / Filtrar por ID de serie

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
limitYes
totalYes
offsetYes
nextCursorNo
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds behavioral context like sorting by newest first and support for status/date filters. It does not disclose rate limits or pagination limits beyond the schema, but the added context is useful.

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 two sentences with an example, front-loaded with the main purpose. It includes bilingual text, which is acceptable but adds length. No unnecessary information.

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 the output schema exists, the description covers the essential functionality: listing, filtering, pagination, sorting. It could mention cursor-based pagination more explicitly, but overall it is complete.

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 coverage is 100%, so all parameters are documented. The description adds context by grouping them (pagination, filters) and giving an example, but does not add significant meaning beyond the schema.

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 it lists invoices with pagination and filters. It distinguishes itself from the sibling 'search_invoices' implicitly by being a broader listing, but does not explicitly mention when to use one over the other.

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

Usage Guidelines3/5

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

The description mentions optional pagination and filters, and provides an example. However, it does not discuss alternatives like 'search_invoices' or specify conditions when not to use this tool.

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/berthelius/frihet-mcp'

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