Skip to main content
Glama

Banco Bmg MCP

by io.github.mcp-dir

openfinance_update_transaction_category

Corrects the category of one or more transactions (PATCH /transactions/:id). Pass items as an array of { transaction_id, category_id } — transaction_id comes from openfinance_list_transactions, category_id from openfinance_list_categories. This overrides Pluggy's automatic categorization AND teaches Pluggy: recategorizing a transaction automatically creates a Category Rule for this client (case-insensitive exact match on the transaction's data), so FUTURE similar transactions are categorized the same way — use this to fix miscategorized transactions and improve categorization accuracy going forward. Batch shape: returns { updated, results: [{ transaction_id, category, categoryId }], errors: [{ id, status, message }] } — per-item errors do not fail the whole batch.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes

TDQS

A4.6/5.0
Behavior5/5

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

The description reveals a crucial behavioral detail beyond annotations: recategorizing creates a Category Rule affecting future transactions. Annotations only indicate destructiveHint=false and no idempotentHint, so the description adds significant transparency about side effects.

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

Conciseness4/5

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

The description is relatively long but well-structured, front-loading the core action then providing batch behavior details. Every sentence adds value, though minor tightening could improve conciseness.

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 no output schema, the description fully documents the response format ({ updated, results, errors }) and error handling behavior. The tool has one parameter with clear structure, and the description covers all necessary context for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 0% schema description coverage, the description thoroughly explains the 'items' parameter structure (array of objects with transaction_id and category_id) and tells the agent where to obtain these IDs from sibling tools. This adds essential semantic meaning.

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 the action 'Corrects the category' with the HTTP method and endpoint (PATCH /transactions/:id). It distinguishes from sibling tools by specifying where transaction_id and category_id come from (list_transactions, list_categories).

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 explains when to use it: to fix miscategorized transactions and improve categorization accuracy. It provides explicit sources for input values and mentions the side effect of creating a Category Rule. No explicit '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 Banco Bmg 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
Disambiguation3/5

The openfinance_ tools are mostly distinct by resource/action, but there are several overlapping pairs: list_accounts vs get_accounts_detail, list_credit_card_bills vs get_credit_card_bill, list_transactions vs list_transactions_by_item, and connect vs toolkit_info vs openfinance_list_connections. The descriptions help disambiguate, but an agent could still misselect between these related tools.

Naming Consistency4/5

The core banking tools consistently follow an openfinance_<verb>_<noun> pattern, which is a strong and readable convention. The generic platform tools (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) break that pattern and use mixed naming styles, creating two distinct naming tiers within the same server.

Tool Count3/5

25 tools sits at the upper borderline of what feels reasonable for one server. The Open Finance domain justifies many read/query tools, but the inclusion of platform meta-tools like marketplace, connect, toolkit_info, report_bug, and show_version inflates the count beyond a tightly focused bank-data scope.

Completeness4/5

The Open Finance surface is largely complete: connectors, sync, disconnect, accounts, balances, transactions, categorization, credit card bills, loans, investments, and provider status are all covered. Minor gaps exist, such as the lack of a dedicated investment detail endpoint and limited consent/permission introspection, but agents can work around these with the existing tools.

Resources