Skip to main content
Glama
Sign In
Archiware MCP

Archiware MCP

by mnott
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

start_plan

Starts a real backup job for a plan immediately; requires confirm:true—without it, returns only the command that would run.

Instructions

Starts a real backup job for a plan now. Requires confirm:true; without it only the command that WOULD run is 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": {
      "id": "<id>"
    },
    "name": "start_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPlan id
confirmNoMust be true to actually run

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.6/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 disclose the two critical behaviors: this triggers a real mutating backup, and omitting confirm produces only a preview of the command rather than execution. It does not mention required permissions, side effects on running jobs, or error behavior for an invalid plan id.

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?

Two short sentences, front-loaded with the primary action and the safety gate immediately after. No filler; the only slight compression cost is that the preview behavior is packed into the same sentence as the requirement.

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 two-parameter mutating tool with no annotations and no output schema, the description covers the safety gate well but is silent on what a successful real run returns (job id, status) and on failure modes. Adequate, but an agent still has gaps about outcomes.

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 coverage is 100% and the schema already states that confirm must be true to run, so the baseline is 3. The description reinforces the gate and adds the useful detail that the non-confirm path returns the command that would run, but adds little else about the id parameter.

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: 'Starts a real backup job for a plan now.' The word 'real' implicitly contrasts with a preview/dry-run mode, which helps separate it from the dryrun_plan sibling, but no sibling is named explicitly.

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 confirm:true requirement and the preview fallback imply when the tool will actually execute versus merely report. However, there is no explicit guidance on when to prefer a dry-run or another sibling before committing to a real run.

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