Skip to main content
Glama

Woop 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

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. First observed

TDQS

A5/5.0
Behavior5/5

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

Discloses beyond annotations: overrides automatic categorization, creates a Category Rule for the client affecting future transactions. No contradiction with annotations (readOnlyHint=false, 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?

Single paragraph is dense but clear, front-loads the core action then adds context on effect and response format. Every sentence adds value without redundancy.

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 purpose, usage, parameter details, side effects, and response shape completely. No output schema needed as description provides expected return structure.

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: explains the items array, required fields (transaction_id, category_id) with their sources, and the response shape including batch 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?

Description clearly states the tool corrects categories of transactions via PATCH, specifying the resource (transactions), action (correct categories), and distinguishes from sibling tools like listing or category fetching.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly explains when to use (fix miscategorized transactions), how to obtain required IDs from other tools, and describes the side effect of creating Category Rules for future accuracy, guiding appropriate usage.

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

All Woop 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.7/5.0
Disambiguation3/5

Several tools have overlapping purviews—list_transactions vs list_transactions_by_item, get_credit_card_bill vs list_credit_card_bills, and connect vs list_connections vs get_item_status vs provider_status—so an agent could pick the wrong one. The very detailed descriptions disambiguate them, but the tool names alone do not.

Naming Consistency3/5

The openfinance_ prefix provides a clear family and most members use list_/get_/update_ verbs, but there are deviations like openfinance_provider_status (no verb), openfinance_disconnect_bank, and openfinance_force_sync. Platform tools (authenticate, connect, marketplace, toolkit_info) follow a different, less uniform style.

Tool Count3/5

At 25 tools, this sits at the top of the heavy range. Most Open Finance operations are justified given the breadth of banking data, but overlapping tools and the mega-marketplace tool with many sub-actions make the set feel slightly bloated.

Completeness5/5

The Open Finance surface covers list/get/update/disconnect/sync for accounts, transactions, credit card bills, loans, and investments, plus provider health, connection search, and platform-level auth, marketplace, version, and feedback. There are no obvious dead ends or missing lifecycle operations.

Resources