Skip to main content
Glama
PatricioRios

mmex-mcp

by PatricioRios

mmex_payees_update

Update an existing payee in a Money Manager EX database. Modify its name, category, website, notes, and other fields by providing the payee ID.

Instructions

Update an existing payee.

    Args:
        id: The payee ID.
        name: The payee name.
        category_id: Default category ID.
        number: Payee number/reference.
        website: Payee website.
        notes: Notes about the payee.
        active: Whether the payee is active.
        pattern: Pattern for auto-categorization.
        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
nameNo
category_idNo
numberNo
websiteNo
notesNo
activeNo
patternNo
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. The description does not disclose side effects (e.g., database mutation), idempotency, error handling (e.g., what if payee not found?), or required permissions. It only lists parameters, leaving the agent to infer behavior from the 'update' verb. This is insufficient.

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 concise with a clear one-line purpose followed by a parameter list. It avoids fluff but repeats 'Optional if MMEX_DB_PATH/KEY env var is set' for two parameters. Structurally it is effective and easy to parse.

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?

With 10 parameters (1 required) and no schema descriptions, the description provides minimal context. It lacks examples, error scenarios, or relationships between parameters. The tool has an output schema, which might help, but overall completeness is adequate but not thorough.

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?

Schema description coverage is 0%, so the description carries full burden. It provides brief but helpful explanations for each of the 10 parameters (id, name, category_id, etc.), adding meaning beyond the schema types. However, it lacks constraints or relationships (e.g., format of website, meaning of pattern). Still, it adds significant value.

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 payee.' The verb 'update' and resource 'payee' are specific. Among siblings, this tool is distinct from create, delete, get, list, and update_partial, though the description does not clarify whether this is a full or partial update; however, the presence of update_partial suggests this may replace all fields. Overall purpose is clear.

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_payees_update_partial. It does not mention prerequisites (e.g., payee must exist), contexts where this is appropriate, or contraindications. Lack of usage instructions reduces helpfulness.

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