OpenMonetis MCP

Listar transações

list_transactions

Read-onlyIdempotent

Retrieve paginated financial transactions with filters for period, text, type, status, category, account, card, amount, and related fields; return totals plus compact or full item details.

Instructions

Lista transações paginadas com filtros por período, texto, tipo, condição, forma de pagamento, situação, pessoa, categoria, tag, conta, cartão e faixa de valor. Retorna o total e os itens (versão compacta por padrão). Use detail: "full" quando precisar de todos os campos de um item específico.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_transactions"
  }
}

Input Schema

Name	Required	Description	Default
`q`	No	Busca por nome/estabelecimento.
`page`	No
`sort`	No
`type`	No
`detail`	No	compact retorna os campos essenciais; full devolve o objeto completo da API.	compact
`period`	No	Mês de referência (YYYY-MM).
`tagIds`	No
`cardIds`	No
`dateEnd`	No	Data final (YYYY-MM-DD), inclusiva.
`pageSize`	No	Itens por página. Valores aceitos: 5, 10, 20, 30, 40, 50 ou 100.
`payables`	No	Quando true, retorna apenas contas a pagar em aberto.
`condition`	No
`dateStart`	No	Data inicial (YYYY-MM-DD), inclusiva.
`maxAmount`	No
`minAmount`	No
`personIds`	No
`accountIds`	No
`settlement`	No	Filtra por situação: pago, não pago ou dentro de fatura de cartão.
`categoryIds`	No
`paymentMethod`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.3Nov 13, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond them by disclosing the response shape (total plus items) and the important default that items come back in a compact version unless detail is set to "full". It does not cover sort defaults, pagination limits or auth requirements.

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?

Three sentences, front-loaded with the core action and filter scope before the return-shape and detail caveat. Dense but every sentence carries information; only the long filter enumeration is slightly list-heavy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 20-parameter read tool with no output schema, the description correctly covers the return envelope and the compact/full trade-off, which is the highest-risk ambiguity. Gaps remain around default sort behavior, how pagination interacts with large result sets, and the meaning of several uncovered filter parameters.

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?

With 20 parameters and only 40% schema description coverage, the description must carry weight; it does enumerate the filter families (period, text, type, condition, payment method, settlement, person, category, tag, account, card, amount range), which lets an agent map intent to parameters. However it adds no semantics for undocumented parameters like sort, minAmount/maxAmount pairing, or how multiple filters combine, so it only partially compensates.

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?

States a specific verb and resource ("Lista transações") plus pagination and the full set of filter dimensions, so an agent knows exactly what it retrieves. It does not name or contrast itself with any sibling such as export_transactions or list_invoices, leaving that differentiation to inference.

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?

Gives one explicit routing rule for the detail parameter (use "full" when you need all fields of a specific item), which is genuinely actionable. It never says when to prefer this tool over export_transactions or the more specialized list_* siblings, so broader usage guidance is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server