Skip to main content
Glama

Mercado Pago 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?

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds value by listing specific returned fields (quantity, value, netAmount, expenses) and confirming batch support via investment_ids, which is beyond annotation info.

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 two sentences plus a line for bulk support, front-loaded with the core purpose. No unnecessary words; each sentence adds value.

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 4 parameters and no output schema, the description covers return fields, prerequisite, and batch support. Missing pagination details, but overall sufficient for tool selection and invocation.

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% (no parameter descriptions). The description indirectly explains investment_id as the identifier from the prerequisite tool and mentions batch support for investment_ids, but does not explain page/page_size parameters. Adequate but not comprehensive.

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 a specific investment position' and lists transaction types (BUY/SELL/TAX/etc.), distinguishing it from sibling tools like openfinance_list_transactions by specifying the context after openfinance_list_investments.

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?

Provides explicit guidance to 'Use after openfinance_list_investments to get the investment_id,' indicating prerequisite and typical workflow. Does not explicitly state when not to use, but the 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 Mercado Pago 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
Disambiguation5/5

Each tool has a clearly distinct purpose. Even overlapping-looking tools like list_transactions vs list_transactions_by_item are clearly differentiated (per-account vs consolidated per-connection), and get vs list variants follow standard conventions. The marketplace tool bundles multiple actions but is its own meta-tool. No two tools appear to do the same thing.

Naming Consistency4/5

The openfinance_ prefix provides a consistent pattern for banking operations, with clear get/list/update/force_sync verbs. A few non-prefixed meta tools (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) break the pattern, but they represent different functional domains and are still readable. Overall the convention is predictable.

Tool Count3/5

At 25 tools, this is on the heavy side per the calibration guidelines (16-25 feels heavy). However, the breadth of Open Finance resources (accounts, transactions, investments, loans, credit cards, connections, plus meta operations) largely justifies the count. It's borderline and could benefit from consolidation, but it's not excessive.

Completeness4/5

The tool surface covers the domain comprehensively: listing and getting accounts, transactions, investments, loans, credit card bills, connections, status, sync, category management, and provider health. Missing operations are minor (e.g., no explicit 'get single transaction' but list covers it; no create/update on banking data besides category and disconnect). Core workflows are fully supported.

Resources