Skip to main content
Glama
Sign In
mmex-mcp

mmex-mcp

by PatricioRios
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

mmex_categories_delete

Delete a category from Money Manager EX database by providing its ID. Supports SQLCipher encrypted databases.

Instructions

Delete a category from the MMEX database.

    Args:
        id: The category ID to delete.
        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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "mmex_categories_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
db_pathNo
db_keyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It only states that the tool deletes a category, but does not disclose behavioral traits like irreversibility, permissions required, or impact on related records (e.g., transactions).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise, with a clear one-line purpose followed by an Args section. Every sentence is necessary, no fluff, and the most critical information is front-loaded.

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?

While the description covers the action and parameters, it omits what the tool returns (though an output schema exists) and does not address error conditions or edge cases. Given the presence of an output schema, this is acceptable but not fully complete.

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 coverage is 0%, but the description adds significant meaning to all three parameters: id is the category ID to delete, db_path is the database file path with an environment variable fallback, db_key is for encryption. This compensates for the missing schema descriptions, though it could specify constraints on id existence.

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 that the tool deletes a category from the MMEX database, using a specific verb and resource. It distinguishes itself from sibling tools like mmex_categories_get or mmex_categories_list. However, it lacks details on the nature of deletion (e.g., permanent, cascading).

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?

The description provides no explicit guidance on when to use this tool vs. alternatives, such as whether the category must not have associated transactions or subcategories. No prerequisites or conditions are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools