CDF Finance

Listar transações

list_transactions

Read-only

Lista as transações do usuário (inclusive de contas conjuntas onde ele é membro), com categoria/conta/cartão/centro de custo/agente/tags já incluídos, mais recentes primeiro (por date, não por criação). Sem from/to/limit, traz o histórico inteiro — para não estourar o contexto, use limit (e pagine com offset se precisar de mais) ou restrinja com from/to. Para só o que está por vencer/pendente use upcoming_transactions; para totais agregados por mês use analytics_history ou o endpoint de summary.

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
`to`	No	Data ISO — só transações com date <= to. Default: sem limite superior
`from`	No	Data ISO — só transações com date >= from. Default: sem limite inferior
`limit`	No	Limita a quantidade de transações retornadas (mais recentes primeiro). Default: sem limite
`offset`	No	Pula os N primeiros resultados — use com limit para paginar
`userId`	No	Só para planejadores (mobilePlanners): id de um cliente vinculado, para ver as transações dele em vez das próprias. Omitido = transações do próprio usuário autenticado. Retorna 403 se o usuário autenticado não for planejador desse cliente

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 1, 2026

addedInput schema / properties / from

Added value: +{
+  "description": "Data ISO — só transações com date >= from. Default: sem limite inferior",
+  "type": "string"
+}

changedInput schema / properties / limit / description

Previous value: -"Limita a quantidade de transações retornadas (mais recentes primeiro)"New value: +"Limita a quantidade de transações retornadas (mais recentes primeiro). Default: sem limite"

addedInput schema / properties / offset

Added value: +{
+  "description": "Pula os N primeiros resultados — use com limit para paginar",
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / to

Added value: +{
+  "description": "Data ISO — só transações com date <= to. Default: sem limite superior",
+  "type": "string"
+}

addedInput schema / properties / userId

Added value: +{
+  "description": "Só para planejadores (mobilePlanners): id de um cliente vinculado, para ver as transações dele em vez das próprias. Omitido = transações do próprio usuário autenticado. Retorna 403 se o usuário autenticado não for planejador desse cliente",
+  "type": "string"
+}

First observedSep 1, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds valuable behavior beyond those: it lists transactions from joint accounts, includes pre-joined related entities, sorts by date rather than creation, and warns that omitting limit/from/to returns the entire history, which could overflow context. This is substantial behavioral disclosure that goes beyond what annotations provide.

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?

The description is three sentences, front-loaded with core purpose and scope, then default behavior and warnings, then alternative routing. Every sentence earns its place and there is no filler or redundancy.

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

Completeness5/5

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

The description is complete for a list tool with 5 optional parameters. It covers sorting, included relations, default full-history behavior, pagination guidance, context-overflow warning, and explicitly routes to sibling tools for pending/aggregate use cases. The output schema exists, so return-value details are not necessary. Annotations already cover the safety profile.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents each parameter. The description adds value by explaining the combined pagination behavior (limit with offset) and the context-overflow rationale. It does not describe userId, but the schema covers that fully, so no gap exists. The extra warning and usage synthesis lift it above the baseline 3.

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?

The description uses a specific verb and resource ('Lista as transações do usuário') and specifies scope (joint accounts where the user is a member), included related entities (category/account/card/cost center/agent/tags), and sorting order (most recent first by date). It also distinguishes itself from sibling tools by naming upcoming_transactions and analytics_history as alternatives, so an agent can tell it apart without opening other schemas.

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

Usage Guidelines5/5

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

The description explicitly states when to use alternatives: 'Para só o que está por vencer/pendente use upcoming_transactions; para totais agregados por mês use analytics_history'. It also gives concrete usage guidance for avoiding context overflow by using limit/offset and from/to. This is clear, actionable guidance with no ambiguity.

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

All CDF Finance tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.