CDF Finance

Listar faturas de cartão

list_invoices

Read-only

Lista faturas de cartão de crédito (CreditCardInvoice) do usuário, mais recentes primeiro (ano/mês desc), cada uma com o cartão e as transações vinculadas. Sem filtros retorna faturas em qualquer status (aberta, fechada, paga, parcial, vencida) — para só as pendentes de pagamento use list_pending_invoices, que já aplica esse filtro e ordena por vencimento.

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_invoices"
  }
}

Input Schema

Name	Required	Description	Default
`cardId`	No	Filtra por um cartão específico
`status`	No	Filtra por status exato da fatura

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 1, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / cardId

Added value: +{
+  "description": "Filtra por um cartão específico",
+  "type": "string"
+}

addedInput schema / properties / status

Added value: +{
+  "description": "Filtra por status exato da fatura",
+  "enum": [
+    "OPEN",
+    "CLOSED",
+    "PAID",
+    "PARTIAL",
+    "OVERDUE"
+  ],
+  "type": "string"
+}

First observedSep 1, 2026

TDQS

A4.5/5.0

Behavior4/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 useful behavioral detail beyond them: default unfiltered behavior, status coverage, descending year/month ordering, and inclusion of card and transactions. No contradictions found, though it does not mention pagination or result limits.

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 a single dense sentence that front-loads the core purpose, then delivers scoping, sorting, return contents, and the alternative tool reference. Every clause earns its place and there is no fluff.

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?

For a simple list-with-filters tool, the description covers user scope, default behavior, sorting, included associations, and the relevant sibling. Combined with an output schema and read-only annotations, nothing an agent needs to invoke it correctly is missing.

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%, with both cardId and status already documented in the schema. The description reinforces that filters are optional and lists the status set, but it adds little meaning beyond what the schema already provides.

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 states a specific verb ('Lista'), the resource ('faturas de cartão de crédito (CreditCardInvoice)'), and scope ('do usuário'), and differentiates from list_pending_invoices by naming it. Sorting and linked data are also specified, so an agent can identify the tool's exact purpose.

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?

It explicitly tells when to use this tool ('Sem filtros retorna faturas em qualquer status') and when to prefer the sibling ('para só as pendentes de pagamento use list_pending_invoices'), including the alternative's behavior and ordering. This is a clear when/when-not directive.

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.