Skip to main content
Glama
moneywiz-mcp

moneywiz-mcp

by kyledh

moneywiz_delete_trade

DestructiveIdempotent

Delete an investment trade by transaction ID so MoneyWiz restores the linked holding and keeps the ledger consistent.

Instructions

Delete an investment trade and let MoneyWiz restore the holding.

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": {
      "transaction_id": "<transaction_id>"
    },
    "name": "moneywiz_delete_trade"
  }
}

Input Schema

NameRequiredDescriptionDefault
transaction_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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. The description adds real value beyond that by disclosing a cascade: MoneyWiz restores the affected holding, which is behavior an agent could not infer from the annotations or schema. It stays vague about what 'restore' entails (quantity, cost basis, cash), which keeps it short of a 5.

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?

A single sentence with the action front-loaded and the side effect immediately after it, with no filler. Nothing in it is redundant or padding.

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?

This is a destructive mutation with no output schema and an undocumented required id. The description never says what happens when the trade does not exist, whether a previously deleted holding is recreated or merely re-quantified, or what the caller gets back, so an agent cannot predict the outcome beyond 'the holding is restored'.

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?

There is a single required parameter, transaction_id, with 0% schema description coverage, and the description says nothing about it. The name mismatch is genuinely confusing: the tool deletes a trade but takes a 'transaction_id', and the description never clarifies that this must be the trade's underlying transaction identifier rather than a trade id.

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?

The description names a specific verb ('Delete') and a specific resource ('an investment trade'), and scopes it away from a generic transaction delete by calling out the investment trade and the holding side effect. It does not explicitly name which sibling to use instead, but the resource specificity lets an agent separate it from moneywiz_delete_transaction and moneywiz_delete_holding.

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?

Use is only implied by the name and the phrase 'investment trade' — there is no explicit statement of when to pick this over moneywiz_delete_transaction or moneywiz_update_trade, and no prerequisites or exclusions. An agent can infer the context but must reason about alternatives on its own.

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