Skip to main content
Glama
PatricioRios

mmex-mcp

by PatricioRios

mmex_assets_update

Update an existing asset's attributes in a Money Manager EX database, such as name, start date, status, currency, value, change mode, and notes.

Instructions

Update an existing asset.

    Args:
        id: The asset ID.
        name: The asset name.
        start_date: Start date (YYYY-MM-DD).
        status: Asset status.
        currency_id: Currency ID.
        value_change_mode: Value change mode.
        value: Asset value.
        value_change: Value change.
        notes: Notes.
        value_change_rate: Value change rate.
        asset_type: Asset type.
        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
start_dateNo
statusNo
currency_idNo
value_change_modeNo
valueNo
value_changeNo
notesNo
value_change_rateNo
asset_typeNo
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?

With no annotations, the description must disclose behavioral traits. It only lists parameters without explaining update semantics (full replace vs merge), idempotency, or error handling. The mention of db_path and db_key is helpful but insufficient.

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 starts with a clear purpose sentence but then dumps a parameter list, which is redundant with the schema. It is adequately structured but not concise; every parameter line could be removed without losing unique information.

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?

Given the complexity (13 params) and that an output schema exists, the description still misses key context: update behavior (full vs partial), error conditions, and whether all fields are overwritten. It covers env var fallback for db_path/db_key, but overall is incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description repeats parameter names with minimal elaboration. It adds format for start_date (YYYY-MM-DD), but most parameters are just restated from the schema. With 0% schema description coverage, the description should compensate more.

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 states 'Update an existing asset,' which is a clear verb+resource pair. It distinguishes from sibling tools like create, delete, get, list, and update_partial by name, but does not explicitly explain the difference from update_partial.

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 is provided on when to use this tool versus alternatives (e.g., mmex_assets_update_partial). There is no mention of prerequisites, such as whether the asset must exist or how to handle failures.

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