Skip to main content
Glama
moneywiz-mcp

moneywiz-mcp

by kyledh

moneywiz_delete_account_group

DestructiveIdempotent

Delete an account group in MoneyWiz while keeping its accounts, which remain ungrouped. Use the group ID to identify and remove the group without affecting the underlying accounts.

Instructions

Delete an account group. Its accounts stay, ungrouped.

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": {
      "group_id": "<group_id>"
    },
    "name": "moneywiz_delete_account_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and idempotentHint=true, but the description adds the single most important non-obvious behavioral fact: the member accounts are preserved and merely ungrouped. That is exactly the context a caller needs before a destructive action. It does not cover failure behavior (e.g., a nonexistent group_id) or confirmation requirements, so it stays at 4.

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; the core action is front-loaded and the consequence follows immediately. Every word 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 simple one-parameter destructive tool with rich annotations and no output schema, this covers the essentials — what it deletes and what it preserves. The remaining gap is minor: no mention of what happens if the group_id does not exist or how errors surface.

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?

There is one parameter and schema description coverage is 0%, so the description should ideally clarify it. The name group_id is largely self-explanatory from context, but the schema's anyOf of integer or string is not addressed anywhere, and no format or lookup hint is given. Adequate given the parameter is obvious, but no value added.

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?

Names a specific verb and resource ('Delete an account group') and immediately clarifies the scope, so an agent can tell it apart from moneywiz_delete_account, which removes accounts rather than groupings. It does not explicitly distinguish itself from the broader moneywiz_delete_catalog_object sibling, keeping it just shy of a 5.

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?

Usage is only implied: the statement that accounts survive ungrouped signals this tool reorganizes accounts rather than removing them, so an agent can infer that moneywiz_delete_account is the tool for actually removing accounts. There is no explicit when-to-use, precondition, or named alternative.

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