py-ynab-mcp

by duganth

Overview Schema Source Related Servers Discussions Admin

Python

Remote

delete_scheduled_transaction

Remove unwanted scheduled transactions from YNAB by ID. Preview changes with dry run, or specify a budget for deletion.

Instructions

Delete a scheduled transaction from YNAB.

Args: scheduled_transaction_id: Scheduled transaction UUID. budget_id: Budget ID. Defaults to last-used budget. dry_run: Validate and preview without deleting.

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": {
      "scheduled_transaction_id": "<scheduled_transaction_id>"
    },
    "name": "delete_scheduled_transaction"
  }
}

Input Schema

Name	Required	Description	Default
`dry_run`	No
`budget_id`	No
`scheduled_transaction_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jul 12, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are present, so the description bears full responsibility. It mentions the dry_run parameter for validation without deletion, adding transparency. However, it does not state that deletion is irreversible or require confirmation, leaving some behavioral aspects unclear.

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?

The description is concise, using a clear docstring format with an Args section. It is front-loaded with the main purpose and then details parameters. No unnecessary information is present.

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?

Given the existence of an output schema, the description does not need to cover return values. However, as a delete operation with no annotations, it could mention success/failure indicators or error conditions. The description is adequate but leaves some context unaddressed.

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

Parameters4/5

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

With 0% schema description coverage, the description compensates by listing all three parameters and adding meaning: scheduled_transaction_id is a UUID, budget_id defaults to last-used budget, and dry_run validates without deleting. This provides useful context beyond the schema's type definitions.

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

Purpose5/5

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

The description clearly states 'Delete a scheduled transaction from YNAB', identifying the specific verb and resource (delete, scheduled transaction). This distinguishes it from sibling tools like create_scheduled_transaction and update_scheduled_transaction.

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 explicit guidance on when or when not to use this tool is provided. While the purpose is clear, there is no description of prerequisites, such as ensuring the scheduled transaction exists, or mentioning alternatives for similar operations.

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