Skip to main content
Glama
PatricioRios

mmex-mcp

by PatricioRios

mmex_stocks_update_partial

Update specific fields of an existing stock entry in a Money Manager EX database without altering other data.

Instructions

Update an existing stock partially.

    Args:
        id: The stock ID.
        held_at: Account ID where the stock is held.
        purchase_date: Purchase date.
        name: Stock name.
        symbol: Stock symbol.
        num_shares: Number of shares.
        purchase_price: Purchase price per share.
        notes: Notes.
        current_price: Current price per share.
        value: Current total value.
        commission: Commission paid.
        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
held_atNo
purchase_dateNo
nameNo
symbolNo
num_sharesNo
purchase_priceNo
notesNo
current_priceNo
valueNo
commissionNo
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 provided, the description carries full burden. It only mentions the action and lists parameters, but fails to disclose behavioral traits such as side effects, error handling (what if id not found), or safety considerations.

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 structured as a docstring with a list, but it is verbose with 13 parameter lines. The first sentence is concise, but the bulk could be trimmed without losing clarity.

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?

Given the output schema exists, return values are covered. The description covers all parameters, but lacks behavioral context and usage guidelines. It does not explicitly state that only provided fields are updated, which is important for a partial update tool.

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?

The description lists all 13 parameters with brief descriptions, adding value over the schema (0% coverage). However, many descriptions are tautological (e.g., 'num_shares: Number of shares') and do not provide deeper semantics like allowed formats or constraints.

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 stock partially,' specifying the verb (update), resource (stock), and the partial nature. This distinguishes it from the full update sibling tool (mmex_stocks_update) and other stock tools.

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 explicit guidance on when to use partial update vs full update or when not to use. The note about db_path and db_key being optional if env vars are set is useful but does not cover usage context or alternatives.

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