Skip to main content
Glama
moneywiz-mcp

moneywiz-mcp

by kyledh

moneywiz_create_account

Create a MoneyWiz cash, checking, savings, credit card, investment, or forex account with currency, opening balance, and optional grouping. Loan accounts require a separate payment plan.

Instructions

Create an account. Loan accounts are not created here (they need a payment plan).

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

Input Schema

NameRequiredDescriptionDefault
kindYes
nameYes
noteNo
currencyYes3-letter code, e.g. CNY
group_idNo
credit_limitNo
opening_balanceNoStarting balance; may be negative0
statement_end_dayNoCredit cards: statement closing day
include_in_networthNo
auto_clear_transactionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare this is a non-destructive, non-idempotent write with closed-world scope, so safety is covered. The description adds a useful domain constraint about loan accounts, but says nothing about duplicate-name behavior, whether the currency must be pre-registered, or what happens to the returned account.

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?

Two tight sentences, front-loaded with the action and immediately followed by the exclusion. No filler, though the parenthetical rationale is the only substance beyond the verb.

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?

For a 10-parameter mutation tool with 30% schema coverage and no output schema, the description is far too thin. An agent gets no help with the seven optional parameters, the meaning of opening_balance/group_id, or expected results after creation.

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?

The schema has 10 parameters with only 30% description coverage, so the description is expected to compensate — and it adds nothing. It doesn't even note the three required fields (name, kind, currency) or clarify conditional params like credit_limit and statement_end_day for credit cards.

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+resource ("Create an account") and adds a real scope boundary: loan accounts are excluded because they need a payment plan. That separates it from the loan-facing siblings in the catalog, though it doesn't explicitly distinguish itself from moneywiz_create_account_group or moneywiz_update_account.

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?

Gives one explicit when-not condition (loan accounts), which is genuine routing guidance. But it offers no positive when-to-use context and no prerequisites such as whether the currency or group_id must already exist before calling.

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