OpenMonetis MCP

Desfazer importação

delete_import_batch

Destructive

Removes an import batch and all transactions it created; requires confirm: true to proceed. Use it to undo a mistaken or unwanted import in OpenMonetis MCP.

Instructions

Remove um lote de importação e as transações criadas por ele. Exige confirm: true.

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": {
      "batchId": "<batchId>"
    },
    "name": "delete_import_batch"
  }
}

Input Schema

Name	Required	Description	Default
`batchId`	Yes
`confirm`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.3Nov 13, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Beyond the destructiveHint annotation, the description discloses that the deletion cascades to all transactions created by the batch, which is the key behavioral fact an agent needs. It does not state reversibility or permissions, but the cascade disclosure is substantive added context.

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?

Two short sentences, front-loaded with the action and its scope, followed by the precondition. No wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive two-parameter tool with no output schema, the description covers the essential facts: what is deleted, what else is destroyed, and the confirm requirement. Only irreversibility/error behavior is omitted.

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; it documents that `confirm: true` is required, which is not enforced by the schema (confirm is not in required). The `batchId` parameter is only characterized by its uuid format in the schema and gets no explanation in the description.

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 names a specific verb and resource ('Remove um lote de importação') and states the cascade effect on the transactions it created. It is clear what the tool does, though it does not explicitly contrast itself with related siblings such as import_transactions or delete_transaction.

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?

The requirement of `confirm: true` implies a deliberate confirm-step usage, but there is no explicit when-to-use or when-not-to-use guidance (for example, when to undo a batch versus deleting individual transactions). Usage is only implied.

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

Deploy Server