monarch-mcp2

Recurring Remove Recurring Stream

recurring_remove_recurring_stream

Destructive

Delete a recurring stream by its ID to remove or reset it from Monarch Money data. Use when you need to cancel or clear a subscription or recurring transaction entry.

Instructions

Remove recurring stream. This may delete, clear, reset, or otherwise remove data.

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": {
      "recurring_id": "<recurring_id>"
    },
    "name": "recurring_remove_recurring_stream"
  }
}

Input Schema

Name	Required	Description	Default
`fields`	No	Optional dotted output field paths to return, such as ['id', 'merchant.name', 'category.name'].
`output_mode`	No	Output shape to return. Use summary for compact CLI-style defaults, full for complete structured data without raw, and raw for complete structured data including raw payloads.	summary
`recurring_id`	Yes
`session_path`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 5, 2026

TDQS

C2.6/5.0

Behavior2/5

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

Annotations already declare destructiveHint=true, so the description's claim 'This may delete, clear, reset, or otherwise remove data' merely restates destructiveness without adding specific behavioral context. It fails to explain what actually happens (e.g., deletes the stream permanently, closes it, or removes occurrences). No extra insight beyond annotations.

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 description is very short (two sentences) and front-loaded with the primary purpose. However, the second sentence is vague and redundant given the destructiveHint annotation. It is concise but not efficiently informative; it could be replaced with more specific details.

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?

Given the lack of output schema, 4 parameters, and a destructive action, the description is incomplete. It does not describe return values, confirmation, or side effects (e.g., impact on occurrences or summaries). The agent lacks sufficient information to safely invoke this 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 50%, with two parameters (recurring_id, session_path) lacking descriptions. The tool description does not explain any parameters; it only mentions the action. Thus, it adds no meaning beyond the schema, and the undocumented parameters remain ambiguous.

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?

The description clearly states the action: 'Remove recurring stream.' It specifies the resource (recurring stream) and the verb (remove), distinguishing it from sibling tools like get, create, or update. However, the added elaboration 'This may delete, clear, reset, or otherwise remove data' is vague and does not precisely define what removal entails, slightly reducing clarity.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it does not indicate prerequisites (e.g., must exist) or contrast with 'recurring_update_recurring_stream' for modifying vs removing. The sibling list implies context, but the description itself lacks any usage direction.

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

Deploy Server