micro-mcp

Overview Schema Source Related Servers Discussions Admin

Delete a Micro record backup

micro_backup_delete

Destructive

Delete a specific backup record permanently using its UUID and SHA-256 digest, while preserving current project data and local source files.

Instructions

Permanently delete one exact record-only backup without changing current project data or local source.

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": {
      "backupId": "<backupId>",
      "sha256": "<sha256>",
      "confirm": "<confirm>"
    },
    "name": "micro_backup_delete"
  }
}

Input Schema

Name	Required	Description
`path`	No	Micro project directory; defaults to the server working directory
`sha256`	Yes	Exact digest of the selected backup
`confirm`	Yes	Explicit confirmation to permanently delete this exact record backup
`backupId`	Yes	Exact backup UUID from a fresh micro_backups result

Output Schema

Name	Required	Description	Default
`ok`	Yes
`json`	No
`stderr`	Yes
`stdout`	Yes
`command`	Yes
`exitCode`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Aug 30, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already mark this as destructive, but the description adds meaningful context: the deletion is permanent, applies to exactly one record-only backup, and does not mutate current project data or local source. This goes beyond the annotation signal and sets clear safety expectations.

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?

A single sentence carries the core action, the scope, the permanence, and the safety boundary. It is front-loaded with 'Permanently delete' and contains no redundant words.

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

Completeness5/5

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

Given destructive annotations, complete schema descriptions for all parameters, and an existing output schema, the description is sufficiently complete. It tells the agent what is deleted, that deletion is permanent, and what remains untouched, which is all an agent needs to decide whether to invoke it.

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?

All parameters are already well-described in the schema (backupId, sha256, confirm, path), so no heavy lifting from the description is required. The description's 'one exact' and 'record-only' wording loosely reinforces the backupId and sha256 parameters, but adds no syntax or behavioral detail beyond the schema.

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 states a specific verb ('Permanently delete'), a precise resource ('one exact record-only backup'), and explicitly scopes what it does NOT affect ('without changing current project data or local source'). This distinguishes it from micro_record_delete and micro_backup_restore even without naming alternatives.

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 description implies when to use the tool: when the goal is to permanently remove a record-only backup, not to alter current data. However, it does not explicitly name alternatives or state when not to use it, such as pointing to micro_backup_restore for recovery or micro_record_delete for deleting live records.

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

Deploy Server