Skip to main content
Glama

XP 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. 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"
+}
  2. Added
  3. Removed
  4. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive. Description adds critical behavior: error handling without exception, and detailed data integrity cross-checking for mass zeroing, flagging suspect rows. Goes well 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?

Front-loaded with main purpose, but the long data integrity paragraph could be condensed. Bulk support sentence at end. Adequate but not maximally concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers output structure (total, results, warning) and error handling. Missing details on pagination and type filter. For 6-param tool with no output schema, description should be more comprehensive.

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?

Schema coverage is 0%, description only mentions item_ids for bulk support. No explanation of page, page_size, type, item, or item_id parameters. Agent cannot infer their meanings from description alone.

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?

Description clearly states the tool returns investment portfolio for a connection, listing specific asset types (FIIs, stocks, etc.) and data fields. Differentiates from siblings 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?

Provides context on when to use (investments portfolio), error handling (returns empty response on 403), and bulk support. No explicit when-not-to-use or alternatives, but sibling names imply differentiation.

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

All XP 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.1/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose. The Open Finance tools are granular (e.g., list vs get vs force_sync for different resources), and the marketplace, authentication, and utility tools do not overlap. No two tools could be easily confused.

Naming Consistency4/5

The Open Finance tools consistently use the 'openfinance_' prefix followed by a verb_noun pattern (e.g., list_accounts, get_balance). Other tools (authenticate, connect, marketplace) use simple verb names, which is a minor deviation but still clear and predictable.

Tool Count4/5

25 tools is on the higher end, but the server covers a broad domain (marketplace + comprehensive Open Finance operations). Each tool serves a specific function, and the count is justified by the depth of functionality.

Completeness5/5

The toolset provides full lifecycle coverage for the Open Finance domain: list, get, sync, update, transactions, categories, investments, loans, credit cards, and connections. The marketplace tool is also feature-rich. No obvious gaps for the intended purpose.

Resources