Skip to main content
Glama

BTGPactual 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. Added
  4. Removed
  5. Added
  6. Removed
  7. Added
  8. Removed
  9. Added
  10. Removed
  11. Added
  12. Removed
  13. 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"
+}
  14. Added
  15. Removed
  16. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations indicate readOnlyHint, idempotentHint, and non-destructive. The description goes beyond by detailing the data integrity cross-check for zeroing positions, explaining the `data_integrity_warning` and `integrity:'suspect_zeroed'` flag, and advising against treating those as real zeros. This is critical behavioral context.

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 front-loaded with the primary purpose and return format. It includes necessary details about data integrity, but the length is reasonable given the complexity. Minor redundancy could be trimmed.

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?

Despite no output schema, the description provides a clear picture of return fields (balance, amount, rates, dueDate, issuer) and error handling. It covers edge cases like upstream errors and mass zeroing, making it sufficiently complete for a read-only, idempotent portfolio list tool.

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 only mentions `item_ids` for bulk support. It does not explain parameters like `item`, `page`, `type`, or `page_size` in meaningful detail, leaving the agent to infer their purposes.

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 explicitly states the tool returns investment portfolio for a connection, listing specific asset types (FIIs, stocks, ETFs, etc.). It clearly differentiates from sibling tools like openfinance_list_investment_transactions and openfinance_get_account_balance by focusing on portfolio summary.

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 advises that the tool returns a graceful response instead of throwing when INVESTMENTS isn't enabled, and mentions bulk support via item_ids. However, it does not explicitly state when to use this tool versus alternatives, though the context makes it clear it's for portfolio overview.

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

All BTGPactual 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

A3.9/5.0
Disambiguation4/5

The openfinance_* family is well-decomposed by resource (accounts, transactions, bills, investments, loans, connections) and by action (list, get, update, sync, disconnect), and the highly detailed descriptions make each tool's boundaries clear. A few pairs can be confused at a glance (list_accounts vs. get_account_balance, list_transactions vs. list_transactions_by_item, connect vs. toolkit_info), but the semantics are ultimately distinguishable.

Naming Consistency3/5

The openfinance_* group follows a strong and consistent verb_noun pattern (list_transactions, get_item_status, force_sync). However, the platform-level tools are a mixed bag—authenticate, connect, marketplace, toolkit_info, show_version, report_bug—so there is no single predictable naming scheme across the whole server.

Tool Count3/5

At 25 tools, the server is at the heavy/borderline boundary, though most of the surface area is genuinely needed for Open Finance reads and connection lifecycle management. Some functions overlap (list_accounts returns balances that get_account_balance also exposes), making the set feel slightly bloated and closer to a two-in-one platform (Open Finance + marketplace).

Completeness4/5

The server covers the full Open Finance discovery and connectivity lifecycle: search, reconnect, force sync, provider health, accounts, transactions, credit cards, investments, loans, and category correction. Gaps like initiating a new connection or executing financial movements are handled through connect URLs rather than direct tools, so the unavoidable dead-end is likely workable and the core read/aggregate domain is well covered.

Resources