Skip to main content
Glama

99Pay 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.7/5.0
Behavior5/5

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

Annotations only provide hints; the description adds critical behavioral details: it overrides automatic categorization, teaches Pluggy by creating a Category Rule, and describes batch error handling (per-item errors do not fail the whole batch).

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 a single informative paragraph that front-loads the purpose, but is slightly dense; every sentence adds value.

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 the complexity of a batch update with side effects (rule creation) and no output schema, the description provides comprehensive context including behavior, required inputs, and error handling.

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?

Schema coverage is 0%, but the description fully compensates by explaining where transaction_id and category_id come from, the batch shape, and that errors are per-item, adding rich 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 explicitly states it corrects the category of transactions via PATCH /transactions/:id, clearly distinguishing it from sibling tools like listing or syncing.

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?

It explains when to use (fix miscategorized transactions) and references openfinance_list_transactions and openfinance_list_categories for input IDs, but lacks explicit when-not-to-use or alternative tools.

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

All 99Pay 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.4/5.0
Disambiguation5/5

Each tool targets a distinct resource and action, with clear separation between general server utilities (authenticate, connect, marketplace) and the openfinance_* family (get/list/search/update per domain). No two tools appear to overlap: list_transactions vs list_transactions_by_item are differentiated by granularity, and get_item_status vs provider_status by scope. The marketplace tool, while broad, is explicitly named and described, so it doesn't cause ambiguity.

Naming Consistency5/5

All 20 openfinance_* tools follow a strict verb_noun snake_case pattern (list_accounts, get_account_balance, force_sync, update_transaction_category, etc.). The five general tools also use snake_case and clear names, maintaining consistency across the set. No mixing of conventions or inconsistent verb styles.

Tool Count4/5

At 25 tools, the set is on the higher end but well-justified for a platform that aggregates Open Finance data and provides a marketplace. The 20 openfinance tools cover distinct banking operations (accounts, transactions, bills, loans, investments, connections, sync, status, search, categories), each addressing a specific need. The 5 general tools handle authentication, connection status, and platform info. No obvious trivial or redundant tools; each earns its place.

Completeness5/5

The tool surface is comprehensive for the stated domain: CRUD-like coverage across financial resources (list/get for accounts, transactions, bills, loans, investments), plus state management (force_sync, disconnect, update_category) and ecosystem support (search_connectors, provider_status, marketplace). It also includes utilities like authenticate, connect, and version/bug reporting. No missing operations that would cause agent failures; the set covers connection lifecycle, data retrieval, and even API diagnostics.

Resources