Skip to main content
Glama
Sign In
Archiware MCP

Archiware MCP

by mnott
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

delete_plan

Deletes a backup plan by plan id, requiring confirm:true to actually run. Use it to remove outdated or unneeded backup plans from a P5 server.

Instructions

Deletes a backup plan. Requires 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": {
      "plan": "<plan>"
    },
    "name": "delete_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
planYesPlan id
confirmNoMust be true to actually run

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description does carry the key safety signal that this is a destructive operation gated by a confirm flag. It omits other important behavior: whether deletion is permanent or recoverable, what happens to existing snapshots/history, and what permissions are needed.

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, front-loaded sentences with zero filler. The destructive action comes first and the guard condition second, which is an effective ordering for a delete tool.

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?

For a destructive, unannotated tool with no output schema, the definition is minimally adequate but thin. It does not address irreversibility, side effects on backups or schedules, or error conditions, which an agent needs before committing to a delete.

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 100%, and both parameters ('plan' as Plan id, 'confirm' as must-be-true) are documented there. The description only restates the confirm requirement, adding no new meaning beyond the schema.

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 uses a specific verb and resource ('Deletes a backup plan'), which is unambiguous about the operation. It does not, however, distinguish this from related siblings such as disable_plan or set_plan_retention, so an agent must reason about the difference itself.

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?

There is no guidance on when to use this versus disable_plan or other plan-lifecycle siblings, and no stated prerequisites (e.g., whether the plan must be stopped first). The only usage-like statement is the confirm:true requirement, which is already encoded in the schema.

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

Deploy Server

Other Tools