Skip to main content
Glama
PatricioRios

mmex-mcp

by PatricioRios

mmex_transactions_update

Modify a transaction in Money Manager EX by its ID, updating fields like account, payee, amount, status, or notes for accurate record keeping.

Instructions

Update an existing transaction.

    Args:
        id: The transaction ID.
        account_id: Account ID.
        to_account_id: Destination account ID.
        payee_id: Payee ID.
        trans_code: Transaction type. Valid values: "Withdrawal", "Deposit", "Transfer".
        amount: Amount.
        status: Transaction status. Valid values: "" (None), "Reconciled", "Void", "Follow up", "Duplicate".
        transaction_number: Transaction number.
        notes: Notes.
        category_id: Category ID.
        date: Transaction date.
        to_amount: Destination amount.
        db_path: Path to the .mmb database file. Optional if MMEX_DB_PATH env var is set.
        db_key: Encryption key for SQLCipher databases. Optional if MMEX_DB_KEY env var is set.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
account_idNo
to_account_idNo
payee_idNo
trans_codeNo
amountNo
statusNo
transaction_numberNo
notesNo
category_idNo
dateNo
to_amountNo
db_pathNo
db_keyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It mentions mutation ('Update') and lists parameters, but does not explain what happens if the id does not exist, whether the update is full or partial, or any side effects. The mention of environment variables for db_path and db_key is helpful but insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is front-loaded with a clear purpose statement but then verbosely lists all parameters in a docstring-style format. While organized, it is not particularly concise; the parameter list could be shortened or made more readable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 14 parameters and no nested objects, the description covers all parameters with some type info and valid values. However, it omits the return value (output schema exists but is not described) and lacks examples or error handling details, leaving the agent partially uninformed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the full burden of parameter semantics. It provides type hints and valid values for trans_code ('Withdrawal', 'Deposit', 'Transfer') and status ('', 'Reconciled', 'Void', 'Follow up', 'Duplicate'), and explains optional fallback for db_path and db_key via environment variables. This adds meaningful context beyond the schema's titles and types.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Update an existing transaction,' using a specific verb and resource. While it clearly indicates modification, it does not differentiate from the sibling tool mmex_transactions_update_partial, which likely performs a partial update. The distinction is implied by the tool name but not explicitly stated.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like mmex_transactions_create, mmex_transactions_delete, or mmex_transactions_update_partial. There are no prerequisites mentioned, such as the requirement that the transaction with the given id must exist.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PatricioRios/mmex_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server