Skip to main content
Glama
Sign In
Archiware MCP

Archiware MCP

by mnott
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

add_plan_folder

Add a single folder to a backup plan as a new task that defines what to back up; requires confirm:true, otherwise only the calls that would run are returned.

Instructions

Adds one folder to a backup plan as a new task (addtask, client localhost, dirlist , enable - verified); a task defines what to back up. Requires confirm:true; without it only the calls that WOULD run are returned.

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>",
      "path": "<path>"
    },
    "name": "add_plan_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesSingle absolute folder path as seen by the P5 container
planYesPlan id
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 supplied, the description carries the full burden and does real work: it discloses the underlying call sequence (addtask, client localhost, dirlist, enable) and, critically, the confirm-gated dry-run behavior where only the calls that WOULD run are returned. It does not address duplicate handling, permissions, or failure modes, which keeps it from 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?

One compact sentence, front-loaded with the action and scope before the parenthetical mechanics. The nested parenthetical is dense but every clause carries information; nothing is redundant.

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 3-parameter mutation tool with no annotations and no output schema, the definition covers the mutation semantics, the confirm gate, and the dry-run return behavior. Missing only error/edge-case behavior (duplicates, invalid paths) and confirmation of post-execution state.

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. The description earns the extra point by explaining the consequence of confirm=false (the would-be calls are returned instead of executed), which adds meaning beyond the schema's terse "Must be true to actually run", and it reinforces that path must be a single folder.

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 states a specific verb and resource ("Adds one folder to a backup plan as a new task") and clarifies the domain concept ("a task defines what to back up"). The phrase "one folder" / "single path" distinguishes it from the plural sibling add_plan_folders, though the parenthetical internal-API jargon (addtask, client localhost, dirlist) is opaque and slightly muddies the statement.

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?

Usage is implied: pick this for a single folder versus the plural bulk variant. It also names the confirm:true precondition. However, it never explicitly states when to choose this over add_plan_folders or create_plan, leaving the routing inference to the agent.

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