Skip to main content
Glama
Frihet-io

Frihet MCP Server

List Expenses

list_expenses
Read-onlyIdempotent

Retrieve expenses sorted by date with optional filters for vendor, category, date range, and pagination. Control result fields, limit, offset, or cursor.

Instructions

List all expenses with optional pagination and date range filters. Returns expenses sorted by date (newest first). Example: from='2026-01-01', to='2026-03-31', limit=50 / Lista todos los gastos con paginacion y filtros de fecha opcionales.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vendorIdNoFilter by vendor ID / Filtrar por ID de proveedor
categoryNoFilter by expense category (e.g. 'office', 'travel') / Filtrar por categoria
fromNoStart date filter (YYYY-MM-DD) / Fecha inicio
toNoEnd date filter (YYYY-MM-DD) / Fecha fin
fieldsNoComma-separated field names to return (e.g. 'id,description,amount') / Campos a devolver
limitNoMax results (1-100) / Resultados maximos
offsetNoOffset / Desplazamiento
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=true and idempotentHint=true, so the description's added value is limited. It discloses the date sorting behavior but omits details like pagination limits or error handling.

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 concise with two clear sentences plus an example. However, the bilingual inclusion may add redundancy for English-only agents, slightly reducing efficiency.

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 tool has 8 parameters and an output schema, the description covers core functionality and sorting but does not mention cursor-based pagination or the fields parameter. Adequate for a list 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?

Schema coverage is 100%, so the schema documents all parameters. The description provides an example that reinforces usage but does not add semantic meaning beyond what the schema already provides. Baseline 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 clearly states the tool lists expenses with optional pagination and date range filters, and specifies the sort order (newest first). However, it does not differentiate from sibling list tools like list_invoices or list_deposits, which limits distinction.

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 explicit guidance on when to use this tool versus alternatives such as list_transactions or search_invoices. The description includes an example but lacks context for appropriate usage or exclusion criteria.

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