Skip to main content
Glama
moneywiz-mcp

moneywiz-mcp

by kyledh

moneywiz_create_holding

Add an investment or forex holding to an account without recording a trade; specify account and symbol to set opening shares, price, or currency position.

Instructions

Add a holding to an investment or forex account without recording a trade.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "account": "<account>",
      "symbol": "<symbol>"
    },
    "name": "moneywiz_create_holding"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
aliasNo
priceNoOpening price per share0
sharesNoOpening share count0
symbolYes
accountYesAccount id, or its exact name
holding_typeNo
currency_positionNoTrue for a currency position in a forex account

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world mutation, so the safety profile is covered. The description adds nothing about the non-idempotent behavior — e.g. what happens if a holding for that symbol already exists — nor about permission requirements or forex-specific effects. For a write tool whose annotation set explicitly flags non-idempotency, that is a meaningful omission.

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?

A single efficient sentence with the resource and scope front-loaded and no filler. Its brevity is a virtue here, though it shades into under-specification covered by other dimensions.

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?

An 8-parameter mutation tool with half its parameters undocumented, no output schema, and a non-idempotent annotation needs more than one sentence. Nothing is said about duplicate handling, forex currency-position semantics, or what the created holding looks like on return.

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 coverage is only 50%, with name, alias, symbol, and holding_type carrying no description in the schema. The description compensates for none of this: it never explains that symbol is required, how account accepts an id or exact name, or when holding_type/currency_position should be set.

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?

States a specific verb ('Add') and resource ('holding'), scoped to 'an investment or forex account', and the clause 'without recording a trade' distinguishes it from trade/transaction creation. It does not name the closer siblings (set_holding_price, set_holding_shares, set_holding_cost_basis), so differentiation from those is left implicit.

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?

The phrase 'without recording a trade' implies the scenario: seeding an opening position rather than booking a transaction. However, there is no explicit guidance on when to use this versus set_holding_price/set_holding_shares for existing holdings, nor any stated prerequisite that the account must already exist.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.