Skip to main content
Glama
moneywiz-mcp

moneywiz-mcp

by kyledh

moneywiz_set_transaction_status

Idempotent

Update a MoneyWiz transaction's status to cleared, pending, reconciled, unreconciled, void, or unvoid so ledger records reflect the correct financial state.

Instructions

Mark a transaction cleared/pending, reconciled, or a cheque void.

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": {
      "transaction_id": "<transaction_id>",
      "status": "<status>"
    },
    "name": "moneywiz_set_transaction_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYes
transaction_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and readOnlyHint=false, so the safety profile is covered. The description adds which statuses are settable, but says nothing about preconditions (must the transaction exist?), what a void does to balances, or whether unvoid is supported despite being in the enum.

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 no filler; the action and the affected state are stated immediately. Its brevity is close to under-specification rather than wasteful, so it earns high but not top marks.

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

Completeness3/5

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

With only two parameters and no output schema, little needs explaining, and annotations cover reversibility and safety. Still, the description leaves the enum's inverse values and any failure/prerequisite behavior undocumented for a mutation tool.

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 must carry parameter meaning, yet it only names a subset of the enum (cleared, pending, reconciled, void) and omits the reverse operations unreconciled and unvoid entirely. 'cleared/pending' also blurs two distinct enum values, and transaction_id is never explained.

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 ('Mark') and resource ('a transaction') plus the state values involved, so the operation is unambiguous. It does not explicitly distinguish itself from the sibling moneywiz_update_transaction, which an agent could reasonably confuse with a status change.

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?

Usage is implied by the enumeration of status transitions (cleared/pending, reconciled, void), which signals 'use this when you only need to change status.' There is no explicit when-not guidance or reference to the overlapping update_transaction sibling.

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