Skip to main content
Glama

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?

Discloses the key side effect of creating a Category Rule that affects future transactions, which goes beyond annotations. Also explains error handling for batch operations, providing essential behavioral context.

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?

Description is comprehensive but slightly verbose. It front-loads the main action and follows with important details, but could be tightened without losing meaning.

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?

Completely addresses complexity: no output schema, yet describes return shape; covers prerequisites, side effects, and batch behavior. Leaves no gaps for effective tool invocation.

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' parameter, required fields, and how to obtain the IDs from other tools.

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 the tool corrects transaction categories, specifies HTTP method and endpoint, and distinguishes from sibling tools like openfinance_list_transactions and openfinance_list_categories by referencing them as sources for 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?

Provides clear context on when to use (fix miscategorized transactions, improve future accuracy) and prerequisites (IDs from specific sibling tools). Lacks explicit exclusion criteria but offers sufficient guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation4/5

Most tools map clearly to a distinct openfinance resource or action (accounts, transactions, bills, investments, loans, connections, provider health), and the platform utilities are a separate family. The only realistically confusable pairs are openfinance_list_transactions vs openfinance_list_transactions_by_item and openfinance_list_accounts vs openfinance_get_accounts_detail, but the descriptions draw sharp boundaries between them.

Naming Consistency4/5

The 19 openfinance_* tools follow a strong openfinance_<verb>_<noun> convention, with only minor exceptions like openfinance_provider_status and openfinance_list_transactions_by_item. The six platform tools mix bare verbs (authenticate, connect), nouns (marketplace, toolkit_info), and verb_noun (report_bug, show_version), but they are clearly a separate utility layer.

Tool Count3/5

25 tools sits at the top of the 'feels heavy' band. The number is defensible for a full Open Finance data product plus platform management tools, but an agent is exposed to a lot of surface area, and the same server mixes a banking-data adapter with a marketplace/utility layer.

Completeness5/5

The openfinance surface covers the full lifecycle: search/connect/reconnect/disconnect banks, force-sync, item status, provider incidents, accounts, balances, transactions per account and per connection, credit-card bills with paid-status derivation, investments and investment transactions, loans, loan detail, and transaction categorization. Platform tools cover auth, connection status, toolkit state, version, bug reporting, and marketplace operations, so there are no obvious dead ends.