Skip to main content
Glama
PatricioRios

mmex-mcp

by PatricioRios

mmex_payees_update_partial

Update specific payee fields in Money Manager EX databases by providing the payee ID and any optional attributes to modify.

Instructions

Update an existing payee partially.

    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, so the description must disclose behavior. It only states 'Update an existing payee partially' with a parameter list, omitting important traits like database modification, idempotency, error handling, or required permissions.

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 single sentence followed by a clear parameter list. It front-loads the action. Some parameter descriptions could be more succinct, but overall efficient and well-structured.

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 and no annotations, the description covers the mechanics but lacks higher-level context. It does not explain how partial update differs from full update, prerequisites, or typical use cases. The output schema exists but its presence is not leveraged.

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 brief descriptions for each parameter (e.g., 'name: The payee name'), but many are near-tautological and lack constraints or detailed semantics. Adds some value but not fully compensates for the lack of schema descriptions.

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 'Update an existing payee partially,' specifying a verb and resource. The 'partially' distinguishes it from a full update tool like mmex_payees_update, and the parameter list supports the partial update functionality.

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 versus the sibling mmex_payees_update or other payee tools. The description says 'partially' but provides no explicit criteria, alternatives, or exclusions.

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