Skip to main content
Glama

Midway 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. Added
  16. Removed
  17. 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"
+}
  18. Added
  19. Removed
  20. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint false), the description adds rich behavioral detail: graceful fallback on 403/upstream errors with a warning field, data-integrity cross-checking when positions mass-zero out, the `data_integrity_warning` and `integrity:'suspect_zeroed'` flags, and explicit guidance not to treat suspect zeros as real balances. This far exceeds what annotations alone provide and does not contradict them.

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 long but front-loaded with the purpose, then covers error handling and a critical data-integrity scenario. Every sentence delivers meaningful operational guidance, though the asset-type list and row-field enumeration could be trimmed or structured more tightly. Overall it earns its length for a financial data tool.

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, no output schema, and sparse parameter schema, the description covers return fields, error fallback shape, bulk support, and an important edge case with detailed handling instructions. It omits the normal top-level response shape and pagination/filter parameter behavior, which would make it fully complete, but it is still substantially informative.

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 6 parameters and 0% schema description coverage, the description carries the burden but only mentions `item_ids` (for bulk support). It does not explain `item`, `item_id`, `page`, `page_size`, or `type` semantics, nor the distinction between `item`/`item_id`/`item_ids`. The enum for `type` exists but no guidance is given on its use as a filter.

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 uses a specific verb ('Returns') with a clearly identified resource ('investment portfolio for a connection') and enumerates the asset types included. It distinguishes itself from siblings like openfinance_list_investment_transactions by focusing on portfolio positions rather than transaction history.

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 implies when to use the tool: for a connection with the INVESTMENTS product enabled, and it mentions bulk support via item_ids. However, it never explicitly contrasts this with alternatives (e.g., when to use openfinance_list_investment_transactions instead) or states 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 Midway 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
Disambiguation3/5

The openfinance_* family is largely well-differentiated by resource and action, but the monolithic `marketplace` tool bundles search, invoke, install, billing, and prompt-library actions into one name, creating ambiguity about where platform capabilities live. Additionally, `openfinance_list_transactions` and `openfinance_list_transactions_by_item` both return transaction data and could be misselected despite their different aggregation intent.

Naming Consistency3/5

The openfinance_* tools consistently follow a clear verb_noun pattern, which gives the majority of the surface a predictable shape. But the generic platform tools mix bare verbs (`authenticate`, `connect`), nouns (`marketplace`, `toolkit_info`), and verb_noun names (`report_bug`, `show_version`), so the server has two naming dialects rather than one uniform convention.

Tool Count3/5

At 25 tools, this sits right at the top of the heavy range, and the server genuinely spans two broad domains: MCP platform administration and Open Finance banking data. The count is defensible given the breadth, but it is not a lean or easily navigable surface for an agent.

Completeness4/5

The Open Finance side is quite complete, covering connections, accounts, transactions, credit card bills, loans, investments, categories, provider status, sync, and disconnection. The platform side covers authentication, connection status, marketplace operations, bug reporting, and versioning, though some marketplace sub-actions are packed into one tool and bank connection itself is only reachable through URLs returned by other tools.

Resources