Skip to main content
Glama
Sign In
Archiware MCP

Archiware MCP

by mnott
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

task_set_directories

Replaces a backup task's directory list, verifies the stored paths by reading them back, and restores the previous list with an error if they do not match. Requires confirm:true.

Instructions

Replaces the directory list of a backup task, reads it back and reports before/after; if P5 did not store exactly the requested list the old value is restored and an error is returned. 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": {
      "task": "<task>",
      "directories": "<directories>"
    },
    "name": "task_set_directories"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesTask id
confirmNoMust be true to actually run
directoriesYesAbsolute paths as seen by the P5 server

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses verification (read-back), failure semantics (old value restored and an error returned on mismatch), and the confirm gate. It omits permissions, preconditions such as whether the task must be disabled, and what the before/after report contains.

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 tightly packed sentence with the action and its verification/rollback behavior front-loaded and the confirm requirement last. No filler.

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 three-parameter mutation with no annotations and no output schema, the description covers purpose, atomicity/rollback, and the safety gate. The main gap is the shape of the before/after report and any task-state preconditions, which the absence of an output schema leaves undocumented.

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 baseline is 3, and the description adds genuine meaning beyond it: 'directories' is the complete replacement list, and confirm must be true for the operation to execute. That clarifies the destructive-vs-additive semantics the schema itself does not spell out.

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 gives a specific verb and resource: it replaces (not appends) the directory list of a backup task, then reads it back. That replacement framing implicitly separates it from add_plan_folder-style siblings, though no sibling is named outright.

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 rather than stated: 'Replaces the directory list' tells an agent this is the full-overwrite tool rather than an additive one, and the confirm gate signals a deliberate action. There is no explicit when-to-use/when-not-to-use guidance and no named alternative for partial edits.

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