Skip to main content
Glama
moneywiz-mcp

moneywiz-mcp

by kyledh

moneywiz_delete_catalog_object

DestructiveIdempotent

Delete an unused category, payee, or tag from a MoneyWiz ledger; if the object is in use, merge it instead.

Instructions

Delete an unused category, payee or tag. In-use objects must be merged instead.

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": {
      "object_type": "<object_type>",
      "object_id": "<object_id>"
    },
    "name": "moneywiz_delete_catalog_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
object_idYesId, or a category path
object_typeYes

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 and idempotentHint=true, so the safety profile is covered. The description adds a genuine behavioral constraint beyond the annotations: deletion is only valid for unreferenced objects, and in-use objects require a merge instead, which is exactly the failure mode an agent needs to avoid.

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, no filler, with the precondition and the corrective action front-loaded. Every clause carries information the agent needs.

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, idempotent delete with no output schema and only two required params, the definition covers the critical decision point (unused vs. in-use). What remains unstated is the effect on any historical references and what an error looks like, which is a modest gap rather than a blocking one.

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 coverage is 50%: object_id is documented as "Id, or a category path" while object_type is an enum that is self-explanatory. The description adds nothing about parameters, notably omitting that object_id accepts a category path for the category type, so it neither helps nor hurts much relative to the schema.

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 (Delete) plus the exact resource set it applies to (category, payee, tag), so the agent knows the scope without opening the schema. It also implicitly separates itself from the merge operation by naming merging as the path for the other case, though it never names the sibling tool itself.

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?

"Delete an unused category..." gives an explicit precondition, and the second clause gives the negative case plus an alternative action (merge). The main gap is that it doesn't point to a way to determine whether an object is in use, despite a catalog_usage sibling existing.

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