Skip to main content
Glama
PatricioRios

mmex-mcp

by PatricioRios

mmex_transactions_update_partial

Update specific fields of an existing transaction in a Money Manager EX database without overwriting other data.

Instructions

Update an existing transaction partially.

    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
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It lists all parameters but does not disclose side effects, authentication requirements, or what happens to omitted fields (likely unchanged). The description is adequate but lacks behavioral depth.

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 structured as a bullet-like list, front-loading the key action. It is not overly verbose, though some parameter explanations could be slightly more concise. Overall, it is efficient and easy to scan.

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 the complexity (14 parameters, 1 required) and the existence of an output schema, the description adequately covers all parameter meanings. However, it lacks context on error conditions, expected behavior of partial updates, and relationship to sibling transaction tools. Slightly incomplete for an agent to use confidently.

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 description coverage is 0%, but the description adds significant meaning by detailing each parameter with valid values (e.g., trans_code: 'Withdrawal', 'Deposit', 'Transfer') and explanation of optional database path and key. This fully compensates for the lack of schema descriptions.

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 states 'Update an existing transaction partially.' which clearly identifies the action (update) and resource (transaction), and the word 'partially' distinguishes this tool from the full update sibling (mmex_transactions_update).

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?

The description does not provide guidance on when to use this tool vs alternatives like mmex_transactions_update. There is no explanation of prerequisites, when a partial update is appropriate, or what fields can be left null. The implied usage is not explicitly stated.

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