Skip to main content
Glama
moneywiz-mcp

moneywiz-mcp

by kyledh

moneywiz_create_tag

Create a new tag in your MoneyWiz ledger by specifying a name. Use it to organize and label transactions through the MCP server before they are synced by the app.

Instructions

Create a tag.

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_tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that — it does not say what happens on duplicate names, whether the tag is returned, or whether creation is scoped to a catalog.

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?

The single sentence is front-loaded and free of waste, but its brevity reflects under-specification rather than efficiency. There is no structure to speak of 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?

For a mutation tool with no output schema, the description should at least indicate the return value or duplicate-handling behavior. Given the annotations cover only the safety profile, the definition leaves the agent guessing about the result of the call.

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

Parameters3/5

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

There is a single required parameter, name, whose meaning is self-evident from its title even at 0% schema description coverage. The description adds no constraints (uniqueness, length, case sensitivity), but for a one-param tool the schema is nearly sufficient on its own.

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 tag" restates the tool name (moneywiz_create_tag) almost verbatim, making it a tautology rather than a real explanation. It does name a verb and resource, but gives no scope, no differentiation from siblings like moneywiz_rename_tag, and no hint of what a tag is in this system.

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, no mention of prerequisites, and no reference to alternatives such as moneywiz_list_tags (to check for existing tags) or moneywiz_rename_tag. The agent must infer all usage context from the name alone.

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