Skip to main content
Glama

Banco Sofisa 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.7/5.0
Behavior5/5

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

The description goes well beyond annotations by detailing that recategorization creates a Category Rule for future similar transactions, teaching the system. It also outlines the side effect of overriding Pluggy's automatic categorization, which annotations did not convey.

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 a single paragraph that front-loads purpose and then provides necessary details. While dense, every sentence is informative. It could be slightly more structured with bullet points, but it remains clear and concise.

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 complexity of a batch update with side effects and no output schema, the description covers all essential aspects: input format, ID sources, behavioral implications, error handling, and return shape.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by explaining the structure of the 'items' array, the required fields (transaction_id and category_id), their sources, and the batch response shape including error handling.

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 tool corrects the category of transactions, specifies the REST endpoint (PATCH /transactions/:id), and distinguishes itself from sibling tools like openfinance_list_transactions and openfinance_list_categories by explaining the source of input IDs.

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?

It explicitly states when to use: to fix miscategorized transactions and improve future accuracy. It also explains that transaction_id comes from openfinance_list_transactions and category_id from openfinance_list_categories. However, it does not mention when not to use or provide alternative tools explicitly.

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

All Banco Sofisa 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.3/5.0
Disambiguation4/5

The openfinance_* tools are cleanly separated by resource and action (accounts, transactions, bills, investments, loans, connections), and the list-versus-get patterns are distinguishable. The main weak spots are the broad 'marketplace' tool, which bundles many sub-actions, and mild overlap between list_accounts/get_account_balance and list_transactions/list_transactions_by_item.

Naming Consistency4/5

The banking tools follow a consistent openfinance_<verb>_<noun> convention, with list_/get_ prefixes used predictably. A few deviations like 'provider_status' (missing a verb) and non-prefixed platform tools (authenticate, connect, marketplace, toolkit_info) keep it from being perfectly uniform.

Tool Count4/5

25 tools is on the heavy side, but the Open Finance domain justifies a wide surface: balances, transactions, bills, investments, loans, connections, sync, and provider health each need their own entry points. The platform/meta tools add some bulk but are individually useful.

Completeness5/5

The Open Finance surface covers the full read lifecycle: discover/search connectors, connect via URLs, list and inspect connections, force sync, check provider/connection status, and read accounts, balances, transactions, credit card bills, investments, and loans. It also supports the one clearly expected write operation (transaction category correction), leaving no obvious dead ends in the core domain.

Resources