Skip to main content
Glama

Caixa Econômica Federal MCP

by io.github.mcp-dir

openfinance_list_transactions_by_item

Read-onlyIdempotent

Consolidated cash-flow analysis for a whole bank CONNECTION over a period, in ONE call. Resolves the connection's accounts internally and fans out their transactions, so you do NOT need to call openfinance_list_accounts first nor carry account_id uuids between calls. Pass item (connector_id, connector_name or item_id) to target one bank, or OMIT it to analyze ALL linked banks at once. from/to are ISO dates (YYYY-MM-DD). Default granularity:'monthly' returns a COMPACT summary (no raw rows): total entradas, saídas, saldo_liquido, monthly evolution (por_mes), and top_despesas/top_recebimentos (largest N each), plus a per-account breakdown (by_account). Use this for 'análise anual/mensal', 'fluxo de caixa', 'entradas e saídas', 'maiores gastos/recebimentos'. Set granularity:'raw' to ALSO get every consolidated transaction (heavier — only when itemized rows are needed); combine with detail:'rich' to enrich those rows with merchantInfo (cnpj/cnae/businessName/category) + extra creditCardMetadata (billId, purchaseDate, fees), or detail:'raw' for the full untouched Pluggy object per row, when the connector provides them. type filters BANK or CREDIT accounts. On a connection with many transactions the scan caps at 5000/account and flags truncated:true. May include a provider_incident block when the Open Finance provider has an OPEN incident affecting a connected bank: the totals/rows may be incomplete or wrong until the provider recovers, and reconnecting does not fix it.

Bulk support: accepts item_ids for batched execution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNo
fromNo
itemNo
typeNo
top_nNo
detailNo
item_idNo
item_idsNo
granularityNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added
  2. Removed
  3. Changed2 schema fields changed
    • addedInput schema / properties / item_id
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / item_ids
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  4. Added
  5. Removed
  6. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already mark the tool as readOnlyHint, idempotentHint, and not destructive. The description adds valuable behavioral context: truncation at 5000/account with a 'truncated:true' flag, a possible 'provider_incident' block with implications, and that the default granularity returns a compact summary. This extra information justifies a score above 3.

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 somewhat verbose but well-structured. It starts with the core purpose, then details parameters and behavioral notes. Every sentence adds value, but some phrases are redundant (e.g., 'consolidated' repeated). The length is justified by the tool's complexity, but could be tightened slightly.

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?

With 9 parameters, no output schema, and a complex tool, the description is remarkably complete. It explains the returned data structure (compact summary fields, raw rows, per-account breakdown), truncation behavior, and provider incident handling. No gaps are apparent for effective tool selection and usage.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must fully detail parameters. It does: explains 'item' accepts connector_id, connector_name, or item_id; 'from'/'to' are ISO dates; 'granularity' defaults to 'monthly'; 'detail' options ('compact', 'rich', 'raw') with their effects; 'type' filters BANK or CREDIT; and 'top_n' is implied in 'top_despesas/recebimentos'. 'item_ids' for bulk support is also covered.

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 clearly states the tool's purpose: 'Consolidated cash-flow analysis for a whole bank CONNECTION over a period, in ONE call.' It distinguishes from sibling tools by noting it resolves accounts internally, eliminating the need for openfinance_list_accounts. It also specifies use cases like 'fluxo de caixa' and lists granularity options.

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

Usage Guidelines4/5

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

The description provides explicit guidance on when to use the tool, including specific analysis scenarios ('análise anual/mensal', 'maiores gastos/recebimentos') and how to choose between granularity and detail levels. It also explains when to omit the 'item' parameter for all banks. However, it does not explicitly state when NOT to use this tool in favor of alternatives like openfinance_list_transactions.

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

All Caixa Econômica Federal MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation4/5

Most tools have distinct purposes, especially with the openfinance_ prefix grouping banking operations. However, pairs like openfinance_list_accounts vs openfinance_get_accounts_detail and openfinance_get_credit_card_bill vs openfinance_list_credit_card_bills could cause minor confusion, though descriptions help.

Naming Consistency5/5

Tools consistently use snake_case with a clear verb_noun pattern. Open finance tools all start with openfinance_, and utility tools use simple verbs like authenticate, connect, report_bug. No mixing of conventions.

Tool Count3/5

At 24 tools, the count is on the higher side of the borderline range. The server combines platform management (6 tools) and banking operations (18 tools), which justifies the number, but it feels slightly heavy for a single server.

Completeness5/5

The tool surface covers all major banking operations (accounts, transactions, credit cards, investments, loans) and includes essential maintenance tools (sync, status, disconnect, search connectors). Platform management is also comprehensive with authentication, marketplace operations, and diagnostics.

Resources