Skip to main content
Glama
Frihet-io

Frihet MCP Server

List Invoices

list_invoices
Read-onlyIdempotent

Retrieve a paginated list of invoices with filters for status, client, series, or date range, sorted by newest issue date.

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
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
fromNoStart date filter in ISO 8601 (YYYY-MM-DD) / Fecha inicio
toNoEnd date filter in ISO 8601 (YYYY-MM-DD) / Fecha fin
fieldsNoComma-separated field names to return (e.g. 'id,clientName,total') / Campos a devolver
limitNoMax results per page (1-100, default 50) / Resultados por pagina
offsetNoNumber of results to skip / Resultados a saltar
afterNoCursor for cursor-based pagination (document ID) / Cursor para paginacion basada en cursor

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
totalYes
limitYes
offsetYes
nextCursorNo
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint. Description adds sorting order and filter support beyond annotations, but does not disclose cursor-based pagination or field selection behavior.

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?

Two concise sentences plus an example, but includes redundant Spanish translation. Could be slightly more concise.

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?

Output schema exists, so return values need not be described. Description covers pagination and filtering, but omits mention of cursor-based pagination and the 'fields' parameter. Adequate for most purposes.

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 baseline is 3. Description provides an example but does not add meaningful extra context for parameters beyond what the schema already provides.

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?

Clearly states it lists invoices with pagination and filters, specifies sorting by issue date and filterable fields (status, date range). However, does not distinguish from sibling 'search_invoices' which may have different 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?

No guidance on when to use this tool versus alternatives like search_invoices. No prerequisites or context provided.

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

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