Skip to main content
Glama
moneywiz-mcp

moneywiz-mcp

by kyledh

moneywiz_update_category

Idempotent

Rename a category, move it under another parent, or change its icon and color to update your MoneyWiz ledger structure.

Instructions

Rename a category, move it under another parent, or change its icon.

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": {
      "category": "<category>"
    },
    "name": "moneywiz_update_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconNo
nameNo
colorNo
parentNoParent category, or "" to move to the top level
categoryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

Annotations already cover the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), so the bar is lower, but the description adds nothing beyond them: it does not say that unspecified fields are left untouched, what happens to child categories or existing transactions when re-parenting, or whether the target parent must already exist. That is the kind of context that would earn credit here.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero filler. It is efficient but lean to the point of under-specification given the mutation surface.

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?

Placeholder — see below.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 20% schema description coverage (only 'parent' is documented), a 3 baseline does not apply; the description compensates by naming the semantics of name, parent and icon. It still omits 'color' (a valid parameter) and does not clarify the required 'category' identifier or the top-level convention beyond what the schema already states.

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 and resource ("Rename a category") plus three concrete mutation modes: rename, re-parent, change icon. An agent can distinguish this from create/delete/list category tools by name and description alone, though no sibling is explicitly named.

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?

Implied usage (edit an existing category) but no explicit when-to-use guidance, no prerequisites, and no routing to alternatives such as create_category for new categories. The 'or' phrasing at least implies the fields are optional and independent.

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