Skip to main content
Glama
PatricioRios

mmex-mcp

by PatricioRios

mmex_stocks_update

Update an existing stock record in a Money Manager EX database. Modify details such as name, symbol, number of shares, purchase price, current price, and more.

Instructions

Update an existing stock.

    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, the description must disclose behavioral traits. It only states that the tool updates a stock and lists parameters, but does not explain what happens to omitted fields (whether they are left unchanged or set to null), any side effects like balance updates, or return value details. This leaves significant behavioral ambiguity.

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 docstring with a clear one-line summary followed by a list of parameter descriptions. It is adequately structured but somewhat verbose with 13 parameter lines. The first sentence effectively states the purpose, but the bulk is a flat list without details like validation constraints or formatting hints.

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 13 parameters and 0% schema description coverage, the description is too minimal. It lacks business context such as how updating a stock affects related accounts, validation rules, or the relationship to the sibling partial update tool. The existence of an output schema is mentioned but not detailed, leaving the return value behavior unknown.

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 carries the full burden. It provides brief explanations for each parameter (e.g., 'Account ID where the stock is held'), which adds some meaning beyond the schema types. However, many descriptions are merely restatements of the parameter name (e.g., 'Number of shares'), offering limited added value. Overall, it minimally compensates for the lack of 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 explicitly states 'Update an existing stock,' which clearly identifies the action and resource. This distinguishes it from sibling tools like create, delete, get, list, and update_partial.

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 provides no guidance on when to use this tool versus alternatives like mmex_stocks_update_partial, nor does it mention prerequisites or conditions for updating. The agent is left to infer usage from context.

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