Skip to main content
Glama
PatricioRios

mmex-mcp

by PatricioRios

mmex_accounts_update_partial

Partially update an existing account's fields—like name, type, or balance—in a Money Manager EX database while keeping other values unchanged.

Instructions

Update an existing account partially.

    Args:
        id: The account ID.
        name: The account name.
        account_type: Account type.
        account_num: Account number.
        status: Account status.
        notes: Notes about the account.
        initial_balance: Initial balance.
        currency_id: Currency ID.
        favorite: Whether the account is a favorite.
        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
account_typeNo
account_numNo
statusNo
notesNo
initial_balanceNo
currency_idNo
favoriteNo
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 bears full responsibility for behavioral disclosure. It mentions 'Update an existing account partially' but lacks details on side effects, restrictions (e.g., updating initial_balance after transactions), or any destructive behavior. The description is insufficient for a mutation tool with no annotations.

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 structured as a docstring with an Args section, making it easy to scan. It is concise with no redundant information, though it could be slightly more compact. It earns its length given the number of parameters.

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 the complexity of 11 parameters and the existence of an output schema (which relieves the description from explaining return values), the description adequately names each parameter but does not explain the partial update behavior (e.g., that only provided fields are updated). It is minimally viable but lacks some operational context.

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?

The schema has 0% description coverage, but the description lists all 11 parameters with brief explanations (e.g., 'id: The account ID'). It adds value by clarifying the optional nature of db_path and db_key via environment variables. However, some descriptions are trivial (e.g., 'name: The account name'), yet the overall coverage is good.

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 account partially,' specifying the verb (update), resource (account), and the nature of the operation (partial update). This distinguishes it from the sibling tool mmex_accounts_update, which presumably performs a full update.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage through the word 'partially' but does not explicitly state when to use this tool over mmex_accounts_update or other siblings like mmex_accounts_create. No when-not or alternative scenarios are provided.

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