Skip to main content
Glama
PatricioRios

mmex-mcp

by PatricioRios

mmex_scheduled_update

Update an existing scheduled transaction by providing its ID and modifying fields like account, payee, amount, status, or recurrence.

Instructions

Update an existing scheduled transaction.

    Args:
        id: The scheduled 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.
        trans_date: First transaction date.
        next_occurrence_date: Next occurrence date.
        repeats: Repeat frequency.
        num_occurrences: Number of occurrences.
        to_trans_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
trans_dateNo
next_occurrence_dateNo
repeatsNo
num_occurrencesNo
to_trans_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?

No annotations are provided, so the description must disclose behavioral traits. It only lists parameters with minimal explanations (valid values for trans_code and status, env var fallback for db_path/db_key). It does not describe side effects, data validation, permissions, or what happens to existing scheduled transactions.

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 front-loads the main action in the first sentence but then includes a verbose parameter list. It is adequately concise but could be more structured (e.g., grouping related parameters).

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

Completeness2/5

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

Given 17 parameters, no annotations, and the presence of an output schema, the description lacks completeness. It does not explain the return value, what fields are updatable, or the behavior of updates (e.g., whether it replaces all fields or only provided ones). This leaves significant gaps for agents.

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

Parameters3/5

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

Schema description coverage is 0%; the description does add meaning for some parameters (trans_code valid values, status valid values, db_path/db_key optionality). However, most parameter descriptions merely restate the parameter name (e.g., 'account_id: Account ID.'), which adds little value beyond the schema.

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 clearly states 'Update an existing scheduled transaction,' specifying the verb and resource. However, it does not distinguish from the sibling tool 'mmex_scheduled_update_partial' or clarify whether this is a full or partial update, which might cause confusion.

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 on when to use this tool vs alternatives (e.g., partial update) or prerequisites (e.g., obtaining the ID from list/get). The description only lists parameters without usage context.

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