Skip to main content
Glama
moneywiz-mcp

moneywiz-mcp

by kyledh

moneywiz_create_payee

Create a new payee record in your MoneyWiz ledger so you can assign payers and payees to transactions and keep accounts organized.

Instructions

Create a payee.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive, closed-world write, so the safety profile is covered. The description adds nothing beyond that: it does not say whether creation fails on a duplicate name, whether the new payee is returned, or whether the payee becomes immediately selectable in transactions.

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?

Three words, front-loaded, zero filler — but the brevity is under-specification rather than efficiency. Nothing is wasted because nothing beyond the tool name was said.

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?

With no output schema, no parameter documentation, and a mutation that touches a shared catalog (payees are referenced by transactions and mergeable via moneywiz_merge_catalog_objects), the definition leaves key behavior unstated. An agent can guess how to call it but not what it will do in edge cases.

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 coverage is 0%, so the description would need to compensate, and it does not. The single parameter "name" is self-evident from its title, but the description says nothing about uniqueness constraints, casing, trimming, or length limits that would matter for a payee catalog object.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Create a payee" names a verb and a resource, but it is a verbatim restatement of the tool name moneywiz_create_payee and adds no scope, no result, and no distinction from siblings like moneywiz_rename_payee or moneywiz_list_payees. This is the tautology case rather than a genuinely clarifying purpose statement.

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?

There is no when-to-use guidance at all: nothing about when a payee must be created versus reused, whether duplicates are allowed, or what to do if the payee already exists. The sibling names hint at alternatives, but the definition itself routes nothing.

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