monarch-mcp2

Transactions Delete Transaction Attachment

transactions_delete_transaction_attachment

Destructive

Delete an attachment from a transaction to remove unwanted files or free up storage. Use this action to permanently clear the attachment data from your records.

Instructions

Delete transaction attachment. 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": {
      "attachment_id": "<attachment_id>"
    },
    "name": "transactions_delete_transaction_attachment"
  }
}

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
`session_path`	No
`attachment_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 5, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the description's statement about deleting/clearing/resetting is consistent but adds little additional context. No further behavioral traits (e.g., authorization needs, side effects) are disclosed.

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?

The description is extremely concise with two short sentences. No unnecessary words or repetition. It directly states the purpose without extraneous details.

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 simplicity of the operation (delete by ID) and the presence of annotations for safety, the description is minimally adequate. However, it lacks any mention of return values or side effects beyond the vague 'delete, clear, reset', and does not integrate with sibling tools or usage context.

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?

The input schema has 50% coverage (fields and output_mode described), but the description does not mention any parameter details. The required attachment_id parameter lacks description both in schema and in the tool description, making it unclear what value to provide. The description fails to compensate for the schema's gaps.

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 the action ('Delete transaction attachment') and the resource (attachment of a transaction). It is a specific verb+resource combination that distinguishes from sibling tools like get, list, download, and upload attachments.

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?

The description provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, consequences, or scenarios where deleting an attachment is appropriate. The sibling tools include other attachment operations, so explicit usage context is needed.

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

Deploy Server