Skip to main content
Glama

Rico 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.3/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds value by detailing the transaction list structure, including expenses breakdown, and bulk execution capability, which are not covered by annotations. No contradiction.

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?

Two well-structured sentences: first sentence dense but covers core functionality and returned fields, second sentence provides usage guidance. No fluff, every sentence adds value.

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

Completeness5/5

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

Given the absence of output schema, the description thoroughly enumerates return fields (quantity, value, amount, netAmount, agreedRate, brokerageNumber, expenses). It also explains bulk support and prerequisite tool usage, ensuring the agent has sufficient context to use it 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 description coverage is 0%, so the description must compensate. It explains the purpose of investment_id and investment_ids, but does not describe page or page_size parameters. This leaves gap for pagination parameters, resulting in partial coverage.

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 movement history for a specific investment position, enumerating transaction types (BUY/SELL/TAX/INTEREST/AMORTIZATION/TRANSFER) and key fields. It is easily distinguishable from sibling tools like openfinance_list_investments or openfinance_list_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?

Explicitly advises using this tool after openfinance_list_investments to obtain the investment_id, and mentions bulk support via investment_ids. However, it does not explicitly state when to avoid this tool or compare it directly to alternatives.

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