Skip to main content
Glama
berthelius

Frihet MCP Server

List Expenses

list_expenses
Read-onlyIdempotent

Retrieve expenses with filters like date range, vendor, or category. Supports pagination and returns results sorted newest first.

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
toNoEnd date filter (YYYY-MM-DD) / Fecha fin
fromNoStart date filter (YYYY-MM-DD) / Fecha inicio
afterNoCursor for cursor-based pagination (document ID) / Cursor para paginacion basada en cursor
limitNoMax results (1-100) / Resultados maximos
fieldsNoComma-separated field names to return (e.g. 'id,description,amount') / Campos a devolver
offsetNoOffset / Desplazamiento
categoryNoFilter by expense category (e.g. 'office', 'travel') / Filtrar por categoria
vendorIdNoFilter by vendor ID / Filtrar por ID de proveedor

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, destructiveHint. Description adds sorting behavior and example usage, but no additional details about rate limits, authentication, or response structure beyond schema.

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?

Two sentences plus bilingual example, no redundancy, front-loaded with key 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 output schema and rich annotations, the description covers purpose, sorting, and filters. Could mention that it returns all expenses without filters, but is still adequate.

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 description adds little beyond mentioning optional pagination and date filters. The example provides minimal extra context.

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

Purpose5/5

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

Clearly states it lists expenses with pagination and date filters, and specifies sorting by date (newest first). Differentiates from sibling list tools by focusing on expenses.

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?

Implies usage by describing optional filters and pagination, but does not explicitly state when to use this vs. other list tools or provide any exclusions.

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