Skip to main content
Glama
Sign In
Archiware MCP

Archiware MCP

by mnott
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

library_reconcile

Reconcile tape-library state after moves: compare P5 volume locations with mtx, update the cleaning slot when confirmed, flag plans lacking appendable volumes, and report slots needing manual checks.

Instructions

After moves: compares every volume's P5 location with mtx, checks the cleaning slot (confirm:true updates cleaningSlot in the config if the CLN tape moved) and warns about enabled plan events whose pool has no appendable volume in the library, with the plan's next run time. Reports P5 slot settings that must be checked manually.

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": "library_reconcile"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to actually run; without it only the plan/commands are returned

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the key side effect (confirm:true writes cleaningSlot to config) plus warning behavior. But it is ambiguous whether the comparison/checking itself happens without confirm, since the schema says a non-confirm call only returns the plan/commands — leaving the agent unsure what a read-only call actually produces, and return format is unexplained.

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?

Front-loaded with the timing cue 'After moves', and every clause carries information. It is a long run-on sentence with nested parentheses, which hurts scannability, but there is 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 one-parameter tool with no output schema and no annotations, the description covers what is compared, what is mutated, what is warned about, and what is left to manual review. The main residual gap is what a non-confirm invocation returns, which the schema only gestures at.

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 by tying confirm:true to a specific mutation — updating cleaningSlot when the CLN tape moved — rather than just 'actually run' as the schema says.

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 concrete operations: comparing each volume's P5 location against mtx, verifying the cleaning slot, and warning about plan events lacking an appendable volume. The reconciliation intent is clear and distinct from siblings like library_plan or library_status, though it relies on unglossed domain jargon (P5, mtx, CLN) that an unfamiliar agent must already know.

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?

'After moves' gives a usable triggering condition, and the closing note about P5 slot settings needing manual checks implies a boundary on what the tool resolves. However, no sibling tool is named as an alternative and there is no explicit when-not guidance (e.g., whether to run library_status first).

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