Skip to main content
Glama
moneywiz-mcp

moneywiz-mcp

by kyledh

moneywiz_delete_holding

DestructiveIdempotent

Delete an investment holding from a MoneyWiz ledger. Requires its trades to be removed first, or set delete_trades to true to remove them along with the holding.

Instructions

Delete a holding. Its trades must be gone, or pass delete_trades.

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": {
      "holding_id": "<holding_id>"
    },
    "name": "moneywiz_delete_holding"
  }
}

Input Schema

NameRequiredDescriptionDefault
holding_idYes
delete_tradesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description adds genuinely new behavior: deletion is blocked while dependent trades exist unless delete_trades is passed, which is the key failure mode an agent needs. It does not say whether the deletion cascades to other references or is reversible, leaving a small gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, zero filler, with the primary action first and the blocking condition second. Every clause earns its place and nothing is repeated from the schema or annotations.

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?

For a two-parameter destructive delete with full annotation coverage and no output schema, this covers the operation, its precondition, and its bypass flag. Only the referential side effects of cascading trade deletion are unaddressed, which is a minor gap for a tool of this complexity.

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 must carry parameter meaning. It does explain the non-obvious delete_trades flag implicitly as the way to force removal of existing trades, which is real added value. holding_id is left entirely to its name, and it is not stated whether delete_trades deletes the trades or merely relaxes a check.

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?

Specific verb plus specific resource ("Delete a holding") makes the operation unambiguous, and the resource name distinguishes it from the many sibling delete_* tools (delete_account, delete_trade, etc.). It stops short of explicitly contrasting with an archive/alternative path, so a 5 is not warranted.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states an explicit precondition for invocation: the holding's trades must already be gone, otherwise the caller must set delete_trades. That is actionable when-to-use/when-it-fails guidance. It offers no alternatives (e.g., archiving or deleting trades first via another tool), which keeps it from a 5.

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