Skip to main content
Glama
moneywiz-mcp

moneywiz-mcp

by kyledh

moneywiz_merge_catalog_objects

DestructiveIdempotent

Merge categories, payees, or tags by moving all references to a target and removing the source objects.

Instructions

Merge categories, payees or tags: references move to the target, sources are removed.

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": {
      "object_type": "<object_type>",
      "source_ids": "<source_ids>",
      "target_id": "<target_id>"
    },
    "name": "moneywiz_merge_catalog_objects"
  }
}

Input Schema

NameRequiredDescriptionDefault
target_idYes
source_idsYes
object_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=true, and not read-only, so the safety profile is covered. The description adds the essential mechanism beyond that: references are reassigned to the target and the source records are deleted, which is exactly the consequence an agent needs before invoking a destructive merge. It stops short of stating irreversibility or error behavior.

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

Conciseness5/5

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

One short sentence, front-loaded with the verb and resource list, followed by the side effect. Nothing is padded and nothing important is buried.

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?

For a destructive three-parameter mutation with no output schema, the description covers the core side effect but omits what the call returns, whether the merge is reversible, and any type-consistency constraint. Adequate to select the tool, incomplete for calling it confidently.

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?

Schema description coverage is 0%, so the description must compensate, and it does partially: sources are removed, the target receives the references, and the resource set maps to the object_type enum. It does not say whether multiple source_ids are allowed, that source and target must share the same type, or what happens on an invalid id.

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 (merge) and names the three resource types (categories, payees, tags). An agent can tell this is a consolidation operation distinct from create/delete siblings, though no sibling is named explicitly.

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 only implied by the semantics of merging: an agent can infer it is for consolidating duplicates or retiring a catalog entry into another. There is no explicit when-to-use or when-not-to-use versus moneywiz_delete_catalog_object or moneywiz_catalog_usage, and no prerequisite is stated.

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