Skip to main content
Glama

Unicred 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. Added
  14. Removed
  15. 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"
+}
  16. Added
  17. Removed
  18. First observed

TDQS

A3.8/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. The description adds valuable behavioral details: data integrity checks when multiple positions become zero, cross-referencing transaction history, and flagging suspect_zeroed rows. It also mentions bulk support via item_ids. This goes well beyond the 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 detailed but somewhat verbose. It front-loads the main purpose, then dives into data integrity details. While each sentence adds value, the length could be trimmed for better conciseness. The structure is logical but could be more compact.

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 (multiple investment types, data integrity handling) and lack of output schema, the description provides a comprehensive overview of the response structure and error handling. It does not explain pagination behavior or how to filter by type, but the input schema covers those. Overall, it is fairly complete for an read-only portfolio listing tool.

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 coverage is 0%, so the description must compensate. It explains the purpose of item_ids (bulk support) and enumerates investment types that map to the 'type' enum. However, it does not explain 'item', 'page', or 'page_size' — leaving their semantics unclear. The output field descriptions are detailed, but input parameters are only partially 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 it returns the investment portfolio for a connection, listing specific asset types (FIIs, stocks, etc.). It uses strong verbs like 'returns' and specifies the scope, distinguishing it from siblings like 'openfinance_list_investment_transactions' which focus on individual transactions.

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

Usage Guidelines3/5

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

The description indicates it is for connections with the INVESTMENTS product enabled, and mentions graceful error handling when the feature is not available. However, it does not explicitly guide when to use this tool versus alternatives like 'openfinance_list_investment_transactions', nor does it state when not to use it.

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

All Unicred 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_* tools are clearly separated by resource and action—accounts, transactions, bills, loans, investments, and connection status—so an agent can usually tell them apart. A few pairs remain confusable, notably openfinance_list_transactions vs openfinance_list_transactions_by_item and the monolithic marketplace tool overlapping with report_bug, but the detailed descriptions largely resolve the boundaries.

Naming Consistency4/5

The openfinance_* subset follows a consistent snake_case verb_noun convention (list_accounts, get_item_status, update_transaction_category), and non-openfinance tools like report_bug and show_version fit the same style. The pattern breaks with bare verbs/nouns such as connect, authenticate, marketplace, and toolkit_info, but the domain prefix makes the majority predictable.

Tool Count3/5

25 tools sits at the top of the heavy-but-manageable range, and the Open Finance resource pairs plus platform/marketplace tools each earn some place. The count feels slightly bloated because marketplace bundles many capabilities and several status/sync tools could be consolidated, but the scope is broad enough that the number is defensible.

Completeness4/5

The toolkit covers the core Open Finance surface thoroughly: accounts, balances, transactions, credit-card bills, loans, investments, categories, connection lifecycle, sync, and provider health, plus marketplace and platform plumbing. Minor gaps exist—no direct connect-bank action beyond URLs, no per-transaction get endpoint, and some marketplace operations are only accessible through the single marketplace tool—but standard workflows are not dead-ended.

Resources