Skip to main content
Glama

Dock 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.8/5.0
Behavior5/5

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

Discloses the side effect of creating a Category Rule for the client, teaches the system, and explains per-item error handling. This goes beyond the annotations, which only set readOnlyHint=false and destructiveHint=false.

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?

The description is a single, well-structured paragraph that front-loads the purpose, then provides usage details and side effects without unnecessary words.

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?

Covers input format, side effects, and output shape comprehensively for a mutation tool with no output schema, given the complexity of batch updates and rule creation.

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?

The schema has 0% description coverage, so the description fully compensates by explaining the array structure, required fields (transaction_id, category_id), and their sources (from list 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?

The description clearly states 'Corrects the category of one or more transactions (PATCH /transactions/:id)' and explains how to obtain the required IDs from sibling tools, distinguishing this from list and other mutation tools.

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 guidance on when to use (to fix miscategorized transactions and improve future categorization) and explains the batch shape, but does not explicitly state when not to use or mention alternatives.

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

All Dock 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/5.0
Disambiguation4/5

Most openfinance_ tools target distinct resources (accounts, transactions, bills, loans, investments, connections, categories), so the core surface is clearly separated. However, several pairs could be confused at first glance: list_transactions vs list_transactions_by_item (both return transactions but at different scopes), get_credit_card_bill vs list_credit_card_bills (bill detail vs list of bills), and get_account_balance vs get_accounts_detail (balance snapshot vs full account object). The detailed descriptions help, but the overlap is nontrivial.

Naming Consistency4/5

The openfinance_* tools follow a consistent pattern (list_, get_, update_, search_, force_sync, provider_status, disconnect_bank), all using snake_case with a clear domain prefix. However, the general platform tools (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) have no such prefix or consistent verb_noun pattern, mixing the convention. The finance subset is strong, but the overall set isn't uniform.

Tool Count3/5

At 25 tools, this is at the upper boundary of acceptable for a broad financial domain covering connections, accounts, transactions, credit cards, loans, investments, categories, and provider health. Each tool adds real capability, so it doesn't feel bloated, but it's heavier than typical and pushes the borderline between well-scoped and too many.

Completeness4/5

The surface covers the Open Finance lifecycle thoroughly: connection management (list, reconnect, force sync, disconnect, provider status), account/balance reads, transaction listing (with filters, pagination, rich detail), credit card bills (closed and open/debt), loans, investments, category management, and a connector search. Obvious gaps like a tool for creating connections are handled via widget URLs rather than an API call, so the coverage feels adequate. Minor gaps exist (e.g., no explicit tool for updating a connection's credentials beyond reconnect URLs), but nothing that would block core workflows.

Resources