Skip to main content
Glama
moneywiz-mcp

moneywiz-mcp

by kyledh

moneywiz_create_category

Create an expense or income category in MoneyWiz, optionally nested under a same-kind parent category, to organize transactions and budgets.

Instructions

Create a category, optionally under a parent of the same kind.

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": {
      "name": "<name>",
      "kind": "<kind>"
    },
    "name": "moneywiz_create_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconNo
kindYes
nameYes
colorNo
parentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, closed-world, so the safety profile is covered. The description adds one genuinely useful behavioral constraint beyond them: a parent must be of the same kind. It says nothing about duplicate-name handling, whether the parent must already exist, or what the tool returns if creation fails.

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 tightly written sentence with zero filler and the key constraint front-loaded. It is arguably under-specified rather than verbose, so it earns credit on conciseness while the missing detail is penalized elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A five-parameter creation tool with zero schema coverage and no output schema needs the description to explain parameter formats and the creation result (e.g., a new category identifier). Instead it supplies one constraint, leaving an agent to guess at icon/color encoding and duplicate handling.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries full burden for five parameters, and it only gestures at 'parent' and implicitly 'kind' via 'same kind'. The meaning of 'icon' (string format?), 'color' (bare integer — encoding? palette index?), and name uniqueness rules are entirely unexplained.

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 ('Create a category') plus a scoping note about optional parentage. It reads unambiguously as a mutation in the category family and is naturally distinct from moneywiz_update_category, though it never names a sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this versus list/update/merge alternatives, no prerequisites (must the parent exist already? does the kind have to match an existing tree?), and no exclusions. The only conditional hint is that parent is optional, which is already visible in the schema's defaults.

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