Skip to main content
Glama
PatricioRios

mmex-mcp

by PatricioRios

mmex_currencies_create

Create a new currency entry in the Money Manager EX database with customizable name, symbol, prefix/suffix, decimal and group separators, and conversion rate.

Instructions

Create a new currency in the MMEX database.

    Args:
        name: Currency name (e.g., US Dollar).
        symbol: Currency symbol (e.g., USD).
        pfx_symbol: Prefix symbol (e.g., $).
        sfx_symbol: Suffix symbol.
        decimal_point: Decimal separator (e.g., .).
        group_separator: Group separator (e.g., ,).
        unit_name: Name of the main unit (e.g., Dollar).
        cent_name: Name of the fractional unit (e.g., Cent).
        scale: Number of fractional units per main unit (e.g., 100).
        base_conv_rate: Base conversion rate as decimal string (e.g., 1.0).
        currency_type: Type of currency (Fiat or Crypto).
        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
symbolYes
pfx_symbolNo
sfx_symbolNo
decimal_pointNo
group_separatorNo
unit_nameNo
cent_nameNo
scaleNo
base_conv_rateNo1.0
currency_typeNoFiat
db_pathNo
db_keyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are present, so the description carries full burden. It explains creation and lists parameters, but does not disclose side effects, uniqueness constraints, or error cases.

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 appropriately sized with a clear purpose sentence followed by a parameter list. It is front-loaded and each line adds value, though the parameter list is lengthy.

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 high number of parameters and presence of output schema, the description covers the purpose and all parameters. It mentions optional env vars for db_path/db_key, but lacks details on constraints or errors.

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?

Schema coverage is 0%, but the description adds meaningful descriptions for all 13 parameters (e.g., 'name: Currency name (e.g., US Dollar).'), fully compensating for the missing schema descriptions.

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 'Create a new currency in the MMEX database' with a specific verb and resource, distinguishing it from sibling tools like mmex_currencies_get or mmex_currencies_update.

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?

No explicit when-to-use or when-not-to-use guidance is provided, but the purpose is clear from the name and description. No alternatives are mentioned.

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