Skip to main content
Glama
PatricioRios

mmex-mcp

by PatricioRios

mmex_accounts_create

Add a new account to a Money Manager EX database. Define name, currency, type, balance, and status to manage financial accounts.

Instructions

Create a new account in the MMEX database.

    Args:
        name: The account name.
        currency_id: Currency ID.
        account_type: Account type: Cash, Checking, Term, Investment, CreditCard, Loan, Asset, Shares.
        account_num: Account number.
        status: Account status: Open or Closed.
        notes: Notes about the account.
        initial_balance: Initial balance as decimal string (e.g., '1000.00').
        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
nameYes
currency_idYes
account_typeNoChecking
account_numNo
statusNoOpen
notesNo
initial_balanceNo0
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. It lacks details on side effects, such as immediate database changes, validation behavior, error states, or idempotency. The description only covers what the tool does, not how it behaves.

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 front-loaded with a clear purpose sentence, followed by a structured parameter list. It is not overly verbose, though the 'Args:' section could be more concise. Overall, it is well-organized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (10 parameters, many optional), the description covers all parameters. It lacks examples or typical use cases, but the output schema likely explains return values. The description is fairly complete but could include more context on prerequisites (e.g., existing account types).

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

Parameters5/5

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

The input schema has 0% description coverage, but the tool description provides detailed explanations for all 10 parameters, including default values and allowed values (e.g., account types). This adds significant meaning beyond the schema.

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 verb and resource: 'Create a new account in the MMEX database.' This distinguishes it from sibling tools like mmex_accounts_delete or update, which have different actions.

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 use for creating accounts but does not explicitly state when to use it versus alternatives. There is no mention of when not to use, nor references to other tools for updates or deletions.

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