Skip to main content
Glama

Unicred 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. Added
  16. Removed
  17. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only and idempotent. Description adds value by detailing transaction types (BUY, SELL, etc.) and output fields (quantity, value, expenses). Lacks pagination behavior but overall good added context.

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 paragraphs, no fluff, front-loaded with purpose. Every sentence adds value: purpose, output fields, usage hint, bulk support. Efficient.

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?

Explains output fields in detail and prerequisite usage. Lacks description of pagination parameters (page, page_size) and their behavior, but overall gives a solid understanding of the tool's function.

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 description must compensate. It explains investment_id in context (prerequisite) and investment_ids (bulk). However, page and page_size are not described. Partial coverage but insufficient for full parameter understanding.

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 specific investment positions, listing transaction types and fields. It distinguishes itself from siblings like openfinance_list_transactions by being investment-specific.

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?

States prerequisite: use after openfinance_list_investments to get investment_id. Also mentions bulk support. Does not explicitly exclude alternatives or provide when-not-to-use, but context is clear.

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

All Unicred 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_* tools are clearly separated by resource and action—accounts, transactions, bills, loans, investments, and connection status—so an agent can usually tell them apart. A few pairs remain confusable, notably openfinance_list_transactions vs openfinance_list_transactions_by_item and the monolithic marketplace tool overlapping with report_bug, but the detailed descriptions largely resolve the boundaries.

Naming Consistency4/5

The openfinance_* subset follows a consistent snake_case verb_noun convention (list_accounts, get_item_status, update_transaction_category), and non-openfinance tools like report_bug and show_version fit the same style. The pattern breaks with bare verbs/nouns such as connect, authenticate, marketplace, and toolkit_info, but the domain prefix makes the majority predictable.

Tool Count3/5

25 tools sits at the top of the heavy-but-manageable range, and the Open Finance resource pairs plus platform/marketplace tools each earn some place. The count feels slightly bloated because marketplace bundles many capabilities and several status/sync tools could be consolidated, but the scope is broad enough that the number is defensible.

Completeness4/5

The toolkit covers the core Open Finance surface thoroughly: accounts, balances, transactions, credit-card bills, loans, investments, categories, connection lifecycle, sync, and provider health, plus marketplace and platform plumbing. Minor gaps exist—no direct connect-bank action beyond URLs, no per-transaction get endpoint, and some marketplace operations are only accessible through the single marketplace tool—but standard workflows are not dead-ended.

Resources