Skip to main content
Glama
henfrydls

actual-budget-mcp

by henfrydls
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

delete_category_group

Destructive

Delete a category group permanently after previewing, confirming by exact name, and designating a category to receive orphaned transactions.

Instructions

Delete a category group and every category in it. Destructive and irreversible: the first call only previews, and deleting requires confirm: true plus confirm_name set to the group's exact name. You must specify a category to transfer orphaned categories' transactions to.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupYesCategory group name or ID to delete
confirmNoMust be true to delete. Without it, the tool only previews.
transfer_toYesCategory name or ID to transfer orphaned transactions to
confirm_nameNoThe group's exact name, echoed back as a safeguard.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.8.3
    • addedInput schema / properties / confirm
      Added value: +{
+  "description": "Must be true to delete. Without it, the tool only previews.",
+  "type": "boolean"
+}
    • addedInput schema / properties / confirm_name
      Added value: +{
+  "description": "The group's exact name, echoed back as a safeguard.",
+  "type": "string"
+}
  2. First observedv0.6.1

TDQS

A4.2/5.0
Behavior4/5

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

The description adds significant behavioral context beyond the annotations: it explains the two-step confirmation process (preview first, then confirm with exact name), the irreversibility, and the requirement to transfer transactions. The annotations only state readOnlyHint=false and destructiveHint=true, so this extra detail is valuable and consistent.

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?

The description is concise and front-loaded: it states the action and its destructive nature in the first sentence, then explains the confirmation process and transaction transfer requirement. Every sentence adds crucial information with no fluff or redundancy.

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 tool with no output schema, the description covers the essential operational steps: preview, confirmation, and transfer. It also covers the risk of irreversibility. It does not explicitly state the return value or error handling, but given the complexity and the 100% schema coverage, the description is sufficiently complete for an agent to use it correctly.

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%, so all parameters are documented in the schema. The description reinforces the purpose of 'confirm', 'confirm_name', and 'transfer_to', but does not add new semantics beyond what the schema already provides. The overlap is acceptable, hence a baseline score of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool 'Delete a category group and every category in it', using a specific verb and resource. It is unambiguous and distinguishes this destructive action from sibling tools like 'update_category_group' or 'delete_category'.

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 provides clear usage context: it is destructive and irreversible, requires a confirmation step, and necessitates specifying a transfer target. It implicitly advises caution but does not explicitly name alternative tools for non-destructive needs, though the destructive nature is self-evident.

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

Deploy Server

Other Tools