Skip to main content
Glama

InfinitePay 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

A4.7/5.0
Behavior5/5

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

Beyond the minimal annotations (readOnlyHint=false), the description discloses the significant side effect: creating Category Rules that affect future transactions. It also explains batch behavior (per-item errors don't fail the whole batch) and the return shape, providing comprehensive 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?

The description is information-dense and well-structured, starting with the purpose, then inputs, then side effect and return format. Slightly lengthy but every sentence adds value; could be trimmed slightly without losing clarity.

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 no output schema and complexity (batch update, side effects, error handling), the description is complete: it covers input sources, side effect, return shape, and error behavior. No missing information for correct usage.

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 parameters: items as an array with transaction_id and category_id, and specifies the source of each ID (from openfinance_list_transactions and openfinance_list_categories). This adds complete meaning absent from 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 (PATCH endpoint). It distinguishes from sibling tools like openfinance_list_transactions and openfinance_list_categories by specifying their IDs as inputs and referencing them by name.

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 advises using this tool to 'fix miscategorized transactions and improve categorization accuracy going forward', implying when to use. However, it does not explicitly state when not to use or contrast with alternatives beyond referencing the list tools for ID retrieval.

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

All InfinitePay 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

Most tools have clearly distinct purposes within the openfinance_* namespace, but some close pairs exist: get_account_balance vs get_accounts_detail, list_transactions vs list_transactions_by_item, and get_item_status vs provider_status vs force_sync all require careful reading. The detailed descriptions resolve most ambiguity, but selection is not always instant.

Naming Consistency4/5

The openfinance_* tools follow a consistent snake_case verb_noun pattern (list_accounts, get_account_balance, update_transaction_category, force_sync). However, the generic platform tools like authenticate, connect, marketplace, and toolkit_info break the pattern, and provider_status is a noun phrase rather than verb_noun.

Tool Count3/5

At exactly 25 tools, this sits at the heavy boundary. The Open Finance domain justifies many of them, but the set feels bloated because marketplace alone bundles a large number of sub-operations, and several platform utilities could arguably be consolidated.

Completeness4/5

The Open Finance surface is quite complete: connections, accounts, balances, transactions, credit card bills, investments, loans, categories, sync, status, and provider health are all covered. Minor gaps exist around direct connection creation (delegated to URLs) and single-item transaction detail, but agents can work around them.

Resources