Skip to main content
Glama
PatricioRios

mmex-mcp

by PatricioRios

mmex_assets_update_partial

Partially update an existing financial asset's attributes like name, value, or status in a Money Manager EX database without affecting other fields.

Instructions

Update an existing asset partially.

    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 states only that it updates partially, but does not explain that unspecified fields remain unchanged, any required permissions, write behavior, or side effects. The output schema exists but is not described.

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 begins with a clear one-sentence summary followed by a structured parameter list. It is efficient but could be slightly more concise by omitting parameter names that are self-explanatory from the schema.

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?

For a tool with 13 parameters and an output schema, the description is incomplete. It does not explain the partial update semantics (only provided fields updated), the optionality of db_path/db_key with environment variable fallback, or what the output contains. An output schema exists but is unmentioned.

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?

The description adds meaning to the 13 parameters that have 0% schema coverage by listing each with a brief explanation (e.g., 'Start date (YYYY-MM-DD)'). However, it lacks details like allowed values for status, currency_id, or value_change_mode, and does not validate formats beyond the date.

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 the tool's purpose: 'Update an existing asset partially.' The verb 'update' and resource 'asset' are explicit, and 'partially' distinguishes it from the full update sibling tool. The parameter list further specifies what can be updated.

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 the sibling 'mmex_assets_update' or other asset tools. There is no mention of when partial updates are appropriate or when a full update is needed.

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