Skip to main content
Glama
Archiware MCP

Archiware MCP

by mnott

add_plan_folders

Adds multiple folders to a backup plan as enabled tasks, checks each P5 container path, applies an optional filter, and returns task IDs or errors. Requires confirm:true.

Instructions

Adds several folders to a backup plan, one enabled task each (path checked with test -d in the container; optional task filter). Returns per-path task id or error. 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>",
      "paths": "<paths>"
    },
    "name": "add_plan_folders"
  }
}

Input Schema

NameRequiredDescriptionDefault
planYesPlan id
pathsYesAbsolute folder paths as seen by the P5 container
filterNoOptional filter name applied to each task
confirmNoMust be true to actually run

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: it creates enabled tasks (not draft ones), validates each path with `test -d` inside the container, is gated behind confirm:true, and returns per-path task id or error. It omits what happens on duplicate paths or partial failure, which keeps it short of a 5.

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?

Three short clauses that front-load the action, then behavior, then the confirm gate; nothing is redundant. The telegraphic phrasing ('one enabled task each', 'path checked with test -d in the container') is compact but slightly cryptic on first read.

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?

No output schema exists, and the description does supply the return shape (per-path task id or error), the write semantics, and the confirmation gate. For a 4-parameter mutation tool this is close to complete, with only failure/duplicate-path handling left unspecified.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning about parameter handling: paths are validated before task creation, the filter applies per-task, and confirm must be set to actually execute. The plan id parameter remains unelaborated 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?

States a specific verb and resource ('Adds several folders to a backup plan') plus the cardinality ('several folders, one enabled task each'), which implicitly separates it from the singular add_plan_folder sibling. It never names that sibling explicitly, so the differentiation is inferred rather than stated.

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?

Gives conditional detail (optional task filter, requires confirm:true) but no explicit guidance on when to choose this over add_plan_folder for a single path or over create_plan for a new plan. Usage is implied by the plural framing rather than stated.

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