Skip to main content
Glama

ASA 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 critical side effect: recategorizing creates a Category Rule affecting future transactions. Also explains batch error handling (per-item errors don't fail whole batch) and response shape. Compensates fully for lack of annotations.

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?

Every sentence adds value; no redundancy. Front-loaded with purpose, followed by param details, side effects, and error handling. Efficient and well-structured.

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?

Despite no output schema, description provides complete batch response shape and error handling. Covers purpose, param semantics, side effects, and error mode. No gaps.

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 coverage, description fully explains the `items` parameter: array with required fields, source of each field, and the implication of using it. Adds significant meaning beyond 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?

Clearly states the tool corrects category of one or more transactions, with HTTP method and endpoint. Distinguishes from sibling tools by specifying source of IDs (openfinance_list_transactions, openfinance_list_categories).

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?

Explains when to use (fix miscategorized transactions, improve categorization) and provides guidance on obtaining IDs from sibling tools. Lacks explicit when-not-to-use or alternatives, but context is adequate.

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

All ASA 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
Disambiguation3/5

The openfinance_* family is mostly well-differentiated by resource type, but several tools overlap in purpose: openfinance_get_account_balance, openfinance_get_accounts_detail, and openfinance_list_accounts all return account/balance data, and openfinance_list_transactions versus openfinance_list_transactions_by_item have similar scopes. The marketplace tool also bundles many sub-actions (search, invoke, install, subscribe, report_bug, prompt library) into one tool, and duplicates the standalone report_bug tool. Detailed descriptions help, but an agent could easily misselect among the account and transaction variants.

Naming Consistency4/5

Naming is largely consistent: the finance tools follow a clear openfinance_verb_noun pattern (list_accounts, get_account_balance, force_sync, update_transaction_category). There are minor singular/plural inconsistencies (get_account_balance vs get_accounts_detail, get_credit_card_bill vs list_credit_card_bills) and generic platform verbs like authenticate/connect/marketplace that follow a different style, but the overall pattern is predictable and readable.

Tool Count3/5

25 tools is at the upper boundary of what feels manageable for a server covering platform management, marketplace operations, and a broad Open Finance data domain. The count is defensible given the many resource types (accounts, transactions, bills, loans, investments, connections), but it is heavy and the marketplace tool alone packs a dozen sub-capabilities into one entry, making the surface feel larger than 25 discrete tools.

Completeness5/5

The Open Finance surface is quite complete: connection lifecycle (list, connect, disconnect, force sync, status, provider status), account and balance reads, transactions with categorization support, credit card bills with payment status, loans, investments, and investment transactions. Platform concerns like authentication, versioning, toolkit state, marketplace search/install/invoke, and bug reporting are also covered, leaving no obvious dead ends for the server's stated purpose.

Resources