Skip to main content
Glama
PatricioRios

mmex-mcp

by PatricioRios

mmex_transactions_create

Create a new financial transaction in Money Manager EX. Specify account, payee, amount, and type (withdrawal, deposit, or transfer).

Instructions

Create a new 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.
        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.
        date: Transaction date (YYYY-MM-DD).
        to_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
to_account_idNo
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?

No annotations are provided, so the description carries the full burden. It does not disclose side effects (e.g., impact on account balances), authorization requirements, or constraints beyond parameter types. This is insufficient for safe invocation.

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 a bulleted list that is readable but verbose (13 parameters). While every line adds information, the structure could be tighter by grouping related parameters or omitting trivial notes. The main purpose is front-loaded, which helps.

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 13 parameters (4 required) and an output schema, the description covers all parameters but lacks details on value formats (e.g., amount as decimal, date as YYYY-MM-DD) and business rules (e.g., transfer requires both accounts). It does not explain response behavior or error conditions.

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?

With 0% schema description coverage, the description is the sole source of parameter semantics. It adds valid values for trans_code and status, explains transfer-specific parameters (to_account_id, to_amount), and distinguishes optional fields. However, it lacks details on amount format, date format, and validation rules.

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 starts with 'Create a new transaction in the MMEX database', which is a clear verb+resource combination. The tool's purpose is distinct from its siblings (e.g., update, delete, list), so an agent can easily differentiate it.

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 versus alternatives like mmex_transactions_update or mmex_scheduled_create. It does not mention prerequisites, context, or exclusions, leaving the agent to infer usage from the name alone.

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