Skip to main content
Glama
PatricioRios

mmex-mcp

by PatricioRios

mmex_currencies_update

Update an existing currency's properties in your Money Manager EX database, including name, symbol, format settings, and conversion rate.

Instructions

Update an existing currency in the MMEX database.

    Args:
        id: The currency ID to update.
        name: Currency name.
        symbol: Currency symbol.
        pfx_symbol: Prefix symbol.
        sfx_symbol: Suffix symbol.
        decimal_point: Decimal separator.
        group_separator: Group separator.
        unit_name: Name of the main unit.
        cent_name: Name of the fractional unit.
        scale: Number of fractional units per main unit.
        base_conv_rate: Base conversion rate.
        currency_type: Type of currency.
        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
symbolNo
pfx_symbolNo
sfx_symbolNo
decimal_pointNo
group_separatorNo
unit_nameNo
cent_nameNo
scaleNo
base_conv_rateNo
currency_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?

No annotations are provided, so the description must fully disclose behavioral traits. It only lists parameters without mentioning side effects, permissions, validation, or error behavior. For a mutation tool, this is 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 is a straightforward docstring with parameter list. It is adequately concise but somewhat lengthy due to obvious parameter names. The first sentence is clear and front-loaded.

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 tool's complexity (14 parameters, mutation), the description lacks necessary context such as idempotency, error states, or concurrency. An output schema exists but is not shown; return behavior is not mentioned.

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?

Schema description coverage is 0%, so the description compensates by explaining each parameter's purpose (e.g., 'Path to the .mmb database file.'). However, it adds no constraints, allowed values, or format details, leaving room for improvement.

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 the action: 'Update an existing currency in the MMEX database.' It distinguishes from create/delete/get/list but not from the sibling tool mmex_currencies_update_partial, which targets partial updates.

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_currencies_update_partial, nor any prerequisites (e.g., currency must exist) 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