Skip to main content
Glama
moneywiz-mcp

moneywiz-mcp

by kyledh

moneywiz_create_account_group

Create an account group in MoneyWiz to organize related accounts under one name and currency. Optionally assign a color and include specific account IDs.

Instructions

Create an account group.

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>",
      "currency": "<currency>"
    },
    "name": "moneywiz_create_account_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
colorNo
currencyYes
account_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: no duplicate-name behavior, no note on whether account_ids moves existing accounts into the group, no side effects. For a non-idempotent mutation, that is a meaningful gap.

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

Conciseness3/5

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

One short, front-loaded sentence with no wasted words, but it is under-specified rather than genuinely concise. There is nothing to restructure because there is almost no content.

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 non-idempotent mutation tool with no output schema, zero parameter documentation, and no annotation-level detail on side effects or duplicate handling. An agent would be guessing about required formats and outcome behavior, so the definition is not complete enough for correct invocation.

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

Parameters1/5

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

Four parameters with 0% schema description coverage, and the description names none of them. It gives no meaning for name, currency, color, or account_ids (e.g., whether account_ids must reference existing account IDs, or what the default color value 4 represents). With low coverage the description was required to compensate and does not.

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 an account group. This distinguishes it by name from siblings like moneywiz_update_account_group and moneywiz_delete_account_group, but the description itself does no explicit differentiation or scoping.

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 when-to-use guidance, no prerequisites, no exclusions. Nothing says whether an agent should group accounts first versus creating an account directly via moneywiz_create_account, or what to do if a group with this name already exists.

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