Skip to main content
Glama

BTGPactual MCP

by io.github.mcp-dir

openfinance_list_investment_transactions

Read-onlyIdempotent

Returns the movement history for a specific investment position: BUY / SELL / TAX / INTEREST / AMORTIZATION / TRANSFER. Each row carries quantity, value, amount, netAmount, agreedRate (treasury), brokerageNumber, and itemized expenses (brokerageFee, incomeTax, settlementFee, custodyFee, stockExchangeFee, etc.). Use after openfinance_list_investments to get the investment_id.

Bulk support: accepts investment_ids for batched execution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
page_sizeNo
investment_idYes
investment_idsNo

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. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Discloses return fields and bulk capability beyond annotations. However, does not mention pagination behavior (page, page_size parameters) which is relevant for usage.

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?

Three sentences, efficient and clear. Front-loaded with main action, then usage, then bulk. Minor room for improvement in structure.

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?

Covers main functionality, input, and output fields well given no output schema. Lacks pagination details, but overall adequate for a read-only list 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?

Adds meaning for investment_id (usage context) and investment_ids (bulk), but page and page_size parameters remain unexplained. With 0% schema coverage, the description partially compensates.

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 it returns movement history for investment positions, lists transaction types (BUY, SELL, etc.), and distinguishes from siblings by referencing openfinance_list_investments for obtaining investment_id.

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

Usage Guidelines5/5

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

Provides clear context: use after openfinance_list_investments to get investment_id. Also mentions bulk support for batched execution, guiding when to use multiple IDs.

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