Skip to main content
Glama
moneywiz-mcp

moneywiz-mcp

by kyledh

moneywiz_delete_account

DestructiveIdempotent

Delete a MoneyWiz account and its transactions after confirming the transaction count; archive instead unless permanent removal is intended.

Instructions

Delete an account. Archiving is usually the better choice.

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>"
    },
    "name": "moneywiz_delete_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountYesAccount id, or its exact name
confirm_transactionsNoRequired when the account still has transactions: pass the exact number, which the error message reports. They are deleted with the account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/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 fully carried by structured data; the description's only added signal is the archive recommendation. It does not restate the confirm_transactions safety gate or the fact that transactions are destroyed alongside the account, though the schema covers both, so the added value beyond annotations is modest.

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 with zero filler, and the core operation is front-loaded ahead of the advisory sentence. Every sentence earns its place.

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 destructive two-parameter tool, the annotations cover safety and the schema fully documents the confirmation guard and cascade deletion, so the description does not need to repeat them. It is nearly complete; the only missing piece is an explicit statement of irreversibility, which destructiveHint already implies.

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 100% and both parameters ('account' plus the confirm_transactions gate) are documented in the schema, including the error-message count mechanism. The description adds no parameter meaning of its own, so the baseline of 3 applies.

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 states a specific verb and resource ('Delete an account') in the first three words, so there is no ambiguity about the operation. It also gestures at the relevant sibling behavior ('Archiving') without naming moneywiz_archive_account directly, and says nothing about the other delete_* siblings, so sibling differentiation is partial rather than complete.

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?

'Archiving is usually the better choice' is explicit when-not guidance that steers an agent away from this destructive call toward a softer alternative. It stops short of stating when deletion is the correct choice over archiving, but the routing intent is unmistakable.

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