Skip to main content
Glama

EQI 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. Added
  6. Removed
  7. Added
  8. Removed
  9. Added
  10. Removed
  11. First observed

TDQS

A4.8/5.0
Behavior5/5

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

The description goes beyond annotations by explaining the side effect of creating category rules that affect future categorization, and details batch behavior including per-item error handling. This provides rich 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.

Conciseness5/5

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

The description is concise yet comprehensive, front-loading the purpose, then explaining side effects, then the return shape. Every sentence adds value with no waste.

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?

The description is complete given no output schema: it explains return shape, error handling, and side effects. It covers all necessary context for correct 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?

Despite 0% schema description coverage, the description fully explains the 'items' parameter structure, required fields (transaction_id, category_id), and their sources (from list transactions and list categories). It adds significant meaning beyond the 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 the tool corrects transaction categories via PATCH /transactions/:id. It specifies the batch operation and distinguishes from sibling tools like openfinance_list_transactions and openfinance_list_categories by naming them as data sources.

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 explains when to use the tool (to fix miscategorized transactions) and provides context on sourcing IDs from other tools. It does not explicitly state when not to use, but the usage is clear enough.

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

All EQI 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.1/5.0
Disambiguation4/5

The openfinance_* tools are clearly separated by resource and action, and their detailed descriptions make most choices unambiguous. However, marketplace is a multi-action mega-tool that duplicates report_bug, and openfinance_list_transactions vs openfinance_list_transactions_by_item have some overlap that could cause misselection.

Naming Consistency4/5

The 19 openfinance_* tools follow a consistent and predictable 'openfinance_<verb>_<noun>' pattern. The non-openfinance tools are a mixed set (marketplace, toolkit_info, show_version, report_bug, authenticate, connect), which is readable but not fully uniform.

Tool Count3/5

25 tools lands right at the heavy end of the borderline range. The Open Finance domain genuinely has many distinct resources, but the marketplace tool alone packs in many sub-actions, which makes the total tool count feel more bloated than the domain strictly requires.

Completeness4/5

The surface covers the full Open Finance lifecycle well: connections, sync/disconnect, accounts, transactions, credit card bills, loans, investments, categories, provider health, and platform administration. Minor gaps exist, such as no direct connect/add-bank tool beyond returning a connect_url and no get-single-transaction endpoint, but agents can work around these.

Resources