Skip to main content
Glama

Caixa Econômica Federal MCP

by io.github.mcp-dir

openfinance_list_investments

Read-onlyIdempotent

Returns the investment portfolio for a connection (broker or bank with INVESTMENTS product enabled): FIIs, stocks, ETFs, fixed income (CDB/LCI/LCA/Tesouro), mutual funds, retirement (previdência) and COE. Each row carries balance, amount, amountOriginal, amountProfit, lastMonthRate / annualRate / lastTwelveMonthsRate (when available), dueDate, issuer, ISIN, etc. Returns { total:0, results:[], warning } instead of throwing when INVESTMENTS isn't enabled (403) or other upstream errors. DATA INTEGRITY: when MULTIPLE positions come back as TOTAL_WITHDRAWAL with balance/quantity 0 at once (mass zeroing), the tool cross-checks each position's own transaction history upstream; if the zeroing is contradicted (BUY with no sale/redemption/transfer) the response carries data_integrity_warning and the affected rows are flagged integrity:'suspect_zeroed' — treat those balances as UNAVAILABLE (likely a temporary connector failure publishing zeros), never as real R$0, and do NOT sum them into the portfolio.

Bulk support: accepts item_ids for batched execution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemNo
pageNo
typeNo
item_idNo
item_idsNo
page_sizeNo

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.1/5.0
Behavior5/5

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

The description is highly transparent about behavior: it details error handling for 403, data integrity checks for mass zeroing, and the structure of returned data. Annotations (readOnlyHint, idempotentHint, destructiveHint) are consistent and the description adds valuable behavioral context beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is verbose, with detailed paragraphs on data integrity. While front-loaded with the main purpose, excessive detail about edge cases could be condensed or structured better. Some sentences are long and overloaded with info.

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 the complexity (6 parameters, no output schema, no param descriptions), the description is relatively complete in explaining tool behavior, error handling, and data integrity. However, the lack of parameter documentation reduces completeness, preventing a perfect score.

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

Parameters2/5

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

With 0% schema description coverage, the description should compensate, but it only mentions that item_ids supports bulk execution. It does not explain the meaning or usage of 'item', 'page', 'type', 'page_size', or the relationship between parameters. This is a significant gap.

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 returns investment portfolios for a connection, listing specific types such as FIIs, stocks, ETFs, etc. It uses a specific verb ('List Investments') and distinguishes itself from sibling tools like openfinance_list_investment_transactions.

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 context on when to use the tool (to get portfolio data) and how it handles errors (returns { total:0, results:[], warning } instead of throwing). It also gives specific guidance on handling data_integrity_warning. However, it does not explicitly mention when not to use it or contrast with alternative tools.

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