Skip to main content
Glama
Sign In
Archiware MCP

Archiware MCP

by mnott
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

p5_config_backup

Create consistent, integrity-checked backups of P5 configuration and SQLite index databases while P5 runs, producing restorable copies with manifests and SHA256 checksums.

Instructions

Consistent copy of P5's configuration and SQLite index databases (online sqlite3 .backup, integrity_check on each copy, tar of the rest, SHA256SUMS, manifest) into /p5-config//, restorable without P5. P5 keeps running. Keeps the newest p5ConfigBackupKeep verified copies. status:true lists copies. Requires confirm:true; without it the plan (sources, destination, size, free space) is returned.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "p5_config_backup"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoList existing copies instead
confirmNoMust be true to actually run

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.2/5.0
Behavior5/5

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

With no annotations present, the description carries the full burden and does so: it discloses that P5 keeps running, that copies are verified with integrity_check and SHA256SUMS, that they are restorable without P5, and that retention keeps only the newest p5ConfigBackupKeep verified copies. The dry-run semantics and destroyed/kept behavior are spelled out.

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?

It is dense and front-loaded, leading with what is copied before covering destination, retention, and the gating flag. The parenthetical implementation detail is long but each clause carries operative information; it is tight rather than padded.

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 two-flag tool with no annotations and no output schema, the description covers safety (dry run), side effects (P5 keeps running), retention, and destination layout. The only gap is what a successful confirmed run returns (copy path, verification results) beyond the directory pattern.

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: what status:true actually does (lists copies) and what a missing confirm returns (a plan with sources, destination, size, free space). That is more than the terse schema strings convey.

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 names a specific verb and resource: a consistent copy of P5's configuration and SQLite index databases, with the exact destination path pattern and copy method. It is clear what the tool does, though it never names a sibling (such as container_backup or p5_dr_kit) to contrast with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete mode-selection rules: status:true lists existing copies instead of backing up, and confirm:true is required to run, otherwise a plan is returned. That covers when to use each mode well, but there is no guidance on when to prefer this over the other backup-oriented siblings.

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