Skip to main content
Glama

Rico 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

TDQS

A4/5.0
Behavior4/5

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

Annotations already indicate read-only and idempotent behavior. The description adds transparency about error handling (returns fallback on 403) and data integrity checks for mass zeroing, including the data_integrity_warning flag. This goes beyond annotations, though pagination behavior is not discussed.

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 main purpose and includes necessary details about error handling and data integrity. While slightly lengthy, each sentence provides value. It could be more concise but is not overly verbose.

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 tool's complexity (6 parameters, no output schema), the description covers key aspects: return fields (balance, amount, etc.), error behavior, data integrity warnings, and bulk support. Missing details on pagination and parameter explanations are minor gaps, but overall it provides sufficient context for an AI agent.

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?

The input schema has 6 parameters with 0% schema description coverage. The description only briefly explains the item_ids parameter for batched execution, leaving the purpose of item, page, type, and page_size unclear. It fails to add sufficient meaning beyond parameter names and types.

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 an investment portfolio for a connection, listing specific asset types like FIIs, stocks, ETFs, etc. This distinguishes it from sibling tools like openfinance_list_investment_transactions and openfinance_get_account_balance by detailing the scope and unique features such as data integrity warnings.

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 implies usage by specifying it returns portfolio for a connection and handles errors gracefully (returning a warning instead of throwing). It also mentions bulk support via item_ids. However, it does not explicitly state when to use this tool over alternatives or provide conditions for not using it.

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

All Rico 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/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, especially the openfinance_* family, but there is some overlap: openfinance_list_transactions and openfinance_list_transactions_by_item both cover transaction listing (though the latter is aggregated by connection), and openfinance_get_account_balance vs openfinance_list_accounts both return balance info. Descriptions are detailed enough to guide selection, so ambiguity is limited but present.

Naming Consistency4/5

The 19 openfinance_* tools follow a consistent verb_noun pattern (list_accounts, get_balance, force_sync). The remaining generic tools (connect, authenticate, marketplace, report_bug, etc.) don't share the prefix but use clear verb-style names. Two conventions exist, but within each group naming is predictable and readable.

Tool Count3/5

25 tools is at the high end but supports the dual scope: platform management (connect, auth, marketplace) and comprehensive Open Finance data access (19 tools). The count feels slightly heavy, especially with the massive marketplace tool that bundles many actions into one, but it's justified by the breadth of the financial domain.

Completeness4/5

The Open Finance surface is quite complete: accounts, balances, transactions, bills, loans, investments, categories, connections, sync, and provider status are all covered. Missing minor operations like updating categories is present, but there is no obvious gap like missing update/delete for transactions (not applicable). The platform side is minimal but sufficient for auth and info.

Resources