Skip to main content
Glama
PatricioRios

mmex-mcp

by PatricioRios

mmex_currencies_update_partial

Update specific fields of an existing currency record in a Money Manager EX database to correct or modify currency information.

Instructions

Update an existing currency in the MMEX database partially.

    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?

With no annotations, the description carries full behavioral burden. It only states 'Update an existing currency' without disclosing mutation details, idempotency, validation rules, error handling, or what happens if the ID doesn't exist. It also does not mention that unspecified fields remain unchanged.

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 one-sentence purpose, followed by a structured parameter list. It is concise but the 14-line parameter list could be more succinct, though it remains well-organized.

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, no schema descriptions, sibling differentiation needed), the description omits critical context: what the output looks like (output schema exists but unmentioned), required database state, behavior on invalid ID, and that only provided fields are updated. The 'partial' behavior is only implied.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. However, parameter descriptions are tautological (e.g., 'name: Currency name', 'symbol: Currency symbol') and add no meaning beyond the parameter names. The only meaningful additions are the optionality notes for db_path and db_key.

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 'Update an existing currency in the MMEX database partially', indicating the specific verb (update), resource (currency), and scope (partial). This distinguishes it from the full update sibling tool by the word 'partially'.

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 does not provide any guidance on when to use this tool versus mmex_currencies_update (full update) or other currency tools. It lacks usage context, prerequisites, or exclusions, leaving the agent to infer from the tool name alone.

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