Skip to main content
Glama
PatricioRios

mmex-mcp

by PatricioRios

mmex_scheduled_create

Create a new scheduled transaction in Money Manager EX database. Set account, payee, type, amount, and repeat frequency to automate recurring entries.

Instructions

Create a new scheduled transaction in the MMEX database.

    Args:
        account_id: Account ID.
        payee_id: Payee ID.
        trans_code: Transaction type. Valid values: "Withdrawal", "Deposit", "Transfer".
        amount: Amount as decimal string.
        repeats: Repeat frequency (0=None, 1=Weekly, 2=Bi-Weekly, 3=Monthly, etc.).
        to_account_id: Destination account ID (for transfers).
        status: Transaction status. Valid values: "" (None), "Reconciled", "Void", "Follow up", "Duplicate".
        transaction_number: Transaction number/reference.
        notes: Notes.
        category_id: Category ID.
        trans_date: First transaction date (YYYY-MM-DD).
        next_occurrence_date: Next occurrence date (YYYY-MM-DD).
        num_occurrences: Number of occurrences (0=infinite).
        to_trans_amount: Destination amount (for transfers).
        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
account_idYes
payee_idYes
trans_codeYes
amountYes
repeatsYes
to_account_idNo
statusNo
transaction_numberNo
notesNo
category_idNo
trans_dateNo
next_occurrence_dateNo
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 and does not describe side effects (e.g., database modification), idempotency, or required permissions. The mention of optional db_path and db_key is helpful but insufficient for a create operation.

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 front-loaded with the purpose and uses a clear parameter list format. It is somewhat lengthy but each line adds value. Could be slightly more concise, but overall well-structured.

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?

With 16 parameters and no explanation of return values (despite an output schema existing), the description is incomplete. It does not mention what the tool returns upon success or failure, leaving the agent uncertain about the outcome.

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?

The description adds significant meaning beyond the schema by explaining each parameter, such as 'repeats: Repeat frequency (0=None, 1=Weekly, 2=Bi-Weekly, 3=Monthly, etc.)'. This is especially valuable given the high parameter count (16) and the schema having only titles.

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 clearly states 'Create a new scheduled transaction in the MMEX database', providing a specific verb and resource. It distinguishes this tool from sibling tools like mmex_scheduled_update and mmex_transactions_create.

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 any guidance on when to use this tool versus alternatives, nor does it mention prerequisites or context such as requiring an existing account or payee. There is no mention of when not to use it.

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