Skip to main content
Glama

Rede Celcoin 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.2/5.0
Behavior4/5

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

Annotations indicate readOnly, destructive false, idempotent. Description adds detailed row fields (quantity, value, expenses, etc.) and bulk support, going beyond annotations.

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 concise paragraphs, front-loaded with purpose, then details. No unnecessary words.

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 row contents and prerequisite despite no output schema. Lacks pagination details but overall comprehensive for a 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?

Description covers investment_id and investment_ids but omits page and page_size. With 0% schema description coverage, partial compensation is provided.

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?

Clearly states it returns movement history for investment positions, listing specific transaction types and fields. Differentiates from sibling tools like openfinance_list_investments and 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?

Provides explicit prerequisite: use after openfinance_list_investments to get investment_id. Also mentions bulk support. 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 Rede Celcoin 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
Disambiguation3/5

Most openfinance_* tools target distinct resources and actions, but several overlap in purpose: list_transactions vs list_transactions_by_item, get_credit_card_bill vs list_credit_card_bills, and multiple connection/status tools expose reconnect URLs. The long descriptions help, but the boundaries are not always immediately obvious.

Naming Consistency4/5

The openfinance_* tools follow a consistent list_/get_ verb_noun pattern and share a clear prefix. The smaller platform cluster is less consistent — marketplace, connect, authenticate, show_version, toolkit_info — mixing nouns, bare verbs, and snake_case, but it is a minor deviation overall.

Tool Count3/5

At 25 tools, this sits at the heavy end of acceptable. The Open Finance surface is broad enough to justify many of them, but there is redundancy (e.g. list_transactions_by_item largely wraps list_transactions plus account resolution) and a separate platform-management cluster that makes the set feel sprawling.

Completeness4/5

The Open Finance domain is well covered: connection lifecycle, accounts, balances, transactions, credit-card bills, loans, investments, categories, and provider status are all present, and data flows connect properly between tools. Minor gaps exist, such as no single-transaction fetch or dedicated prompt-management tools, but the marketplace tool fills those roles.

Resources