Skip to main content
Glama

Nubank 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 discloses that it overrides automatic categorization AND teaches Pluggy by creating a Category Rule. It also describes batch behavior with per-item errors not failing the whole batch. Annotations set readOnlyHint=false, consistent with a write operation; description adds significant context 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.

Conciseness4/5

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

The description is detailed but not overly verbose. It front-loads the action and packs necessary information about side effects and error handling. Minor redundancy could be trimmed, but overall efficient.

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 (batch update with side effects, no output schema), the description fully covers behavior, parameter sources, side effects, and error handling. It is complete enough for an agent to use correctly.

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 explains the single parameter 'items' as an array of { transaction_id, category_id } and provides sources for the IDs. This adds necessary meaning beyond the raw schema.

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 corrects the category of transactions via PATCH /transactions/:id, specifying the verb and resource. It distinguishes itself from sibling tools like list tools by indicating it modifies data.

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 provides explicit guidance: 'use this to fix miscategorized transactions and improve categorization accuracy going forward.' It explains the side effect of creating a Category Rule, but does not explicitly state when not to use or alternatives.

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

All Nubank 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 resource/action pairs, but there is real overlap among list_accounts, get_accounts_detail, and get_account_balance, as well as between list_transactions and list_transactions_by_item, and between get_credit_card_bill and list_credit_card_bills. The descriptions are detailed enough to usually resolve ambiguity, but the number of near-overlapping read/status tools makes mis-selection plausible.

Naming Consistency4/5

The 21 openfinance_* tools follow a clear openfinance_<verb>_<noun> convention with predictable verbs like list, get, update, force, disconnect, and search. The non-prefixed platform tools (authenticate, connect, marketlace, report_bug, show_version, toolkit_info) break the pattern but are few enough to keep the naming mostly coherent.

Tool Count3/5

25 tools is at the heavy end for the stated banking domain, and several could reasonably be merged: get_account_balance/get_accounts_detail/list_accounts and list_transactions/list_transactions_by_item overlap in purpose. The breadth of resources covered accounts, cards, loans, investments, connections, and provider health helps justify the count, but it still feels slightly bloated.

Completeness5/5

The Open Finance workflow is thoroughly covered: connect discover, force sync, status checks, accounts, balances, transactions, credit-card bills, loans, investments, category correction, disconnection, and provider health. Edge cases like stale data, consent errors, provider incidents, and cross-connector asymmetries are explicitly handled, leaving no obvious dead ends for an agent.

Resources