Skip to main content
Glama
PatricioRios

mmex-mcp

by PatricioRios

mmex_scheduled_update_partial

Partially update a scheduled transaction's fields like amount, payee, category, or repeats without affecting other details.

Instructions

Update an existing scheduled transaction partially.

    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 fails to mention side effects, idempotency, error handling, or whether partial updates merge or replace fields. The behavior of 'partial' is implied but not explicitly defined (e.g., PATCH semantics).

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 long (over 20 lines) and front-loaded with a clear purpose, but the parameter list dominates. It follows a docstring format with an 'Args' block. Given the 0% schema coverage, the length is somewhat justified, but it could be more concise by moving detailed param info to the schema.

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?

The description covers all parameters and mentions optional db_path/db_key environment variables. However, it lacks information about return values (though output schema exists), error conditions, or prerequisites (e.g., needing a valid database connection). It does not explain the 'partial' update semantics thoroughly.

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%, so the description must compensate. It provides one-line descriptions for each parameter, including valid values for 'status' and 'trans_code', and notes optional env vars for db_path/db_key. However, many descriptions are vague (e.g., 'repeats: Repeat frequency') and lack details like format, range, or constraints.

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 partially,' using a specific verb and resource. However, it does not explicitly differentiate from the sibling tool 'mmex_scheduled_update' (full update), which could cause confusion about when to use each.

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 provides no guidance on when to use this tool vs alternatives like 'mmex_scheduled_update' or 'mmex_scheduled_create'. It merely lists parameters, leaving the agent to infer usage context from the word 'partially'.

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