Skip to main content
Glama

Atacadão 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

TDQS

A4.2/5.0
Behavior4/5

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

The description adds value beyond annotations by detailing the specific fields returned (quantity, value, netAmount, etc.) and the bulk feature. It aligns with annotations (readOnlyHint, idempotentHint, destructiveHint). It could mention pagination behavior but the schema already includes page and page_size, mitigating the gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise: two short sentences plus one for bulk support. It front-loads the purpose and includes necessary details without redundancy or verbosity.

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 has 4 parameters and no output schema, the description covers the main aspects: purpose, prerequisite, bulk support, and field details. It lacks explanation of pagination parameters but they are inferable from the schema. It is fairly complete for an agent to use the tool correctly.

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 explain parameters. It explains the key parameters investment_id and investment_ids (bulk), but does not describe page and page_size, which are self-explanatory but still missing from the description. The explanation of core parameters is sufficient but not complete.

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 movement history for investment positions with specific transaction types (BUY, SELL, etc.) and details the fields returned. It distinguishes itself from sibling tools like openfinance_list_investments and openfinance_list_transactions by specifying the resource and prerequisite usage.

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 explicitly says to use after openfinance_list_investments to obtain the investment_id, providing a clear prerequisite and sequence. It also mentions bulk support for batched execution. However, it does not explicitly state when not to use it or alternative tools for general transactions.

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

All Atacadão 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
Disambiguation4/5

Tools are largely distinct: openfinance_* tools cover specific resources (accounts, transactions, bills, loans, investments) with clear boundaries. Some overlap exists between list_transactions and list_transactions_by_item, and between status/sync tools (get_item_status, force_sync, provider_status), but descriptions are detailed enough to guide selection.

Naming Consistency4/5

The openfinance_* prefix provides strong consistency for the bulk of tools, with clear verb_noun patterns (list, get, update, force_sync). The platform tools (authenticate, connect, marketplace, report_bug, etc.) break the pattern but are few and their names are intuitive. Overall, minor mixing of conventions but readable.

Tool Count4/5

25 tools is on the higher side but appropriate for a comprehensive Open Finance and platform management server. The count includes both data access (accounts, transactions, bills, loans, investments) and platform utilities (authentication, connection state, marketplace). No redundant tools; each serves a clear purpose.

Completeness4/5

The surface covers the core read operations for connected banks (accounts, transactions, bills, loans, investments), connection management (sync, status, disconnect), and category correction. Minor gaps include no get-transaction-by-id and no update for account metadata, but these are not critical for the typical use case of a banking data aggregator.

Resources