Skip to main content
Glama
PatricioRios

mmex-mcp

by PatricioRios

mmex_categories_update

Update an existing category's name, active status, or parent category in a Money Manager EX .mmb database.

Instructions

Update an existing category.

    Args:
        id: The category ID.
        name: The category name.
        active: Whether the category is active.
        parent_id: Parent category ID (null for root).
        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
activeNo
parent_idNo
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 does not mention return values, side effects (e.g., if the category has subcategories), idempotency, or error conditions. The output schema exists but its content 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 is concise with a clear docstring structure. It front-loads the purpose and lists parameters efficiently. Minor redundancy (e.g., repeating 'id: The category ID') could be trimmed, but overall it earns its sentences.

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 presence of an output schema and multiple optional parameters, the description adequately covers parameter semantics but lacks behavioral context (return value, validation, side effects) and usage guidance. It is minimally viable but not rich enough for an agent to use confidently without additional knowledge.

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%, but the description adds value by explaining each parameter, especially 'parent_id' (null for root) and 'db_path'/'db_key' (environment variable fallback). While some descriptions are redundant (e.g., 'name: The category name'), overall it compensates for the missing schema descriptions.

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 category' which specifies the action and resource. However, it does not differentiate from the sibling 'mmex_categories_update_partial' tool, missing an opportunity to clarify full vs partial update semantics.

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 alternatives like 'mmex_categories_update_partial' or other update tools. The description lacks context about prerequisites or when not to use it.

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