Skip to main content
Glama
Sign In
Archiware MCP

Archiware MCP

by mnott
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

tape_load

Loads a tape from a library slot into its matching generation drive, waits until ready, and leaves it loaded; blocks if the library is busy unless forced.

Instructions

Loads the tape in a library slot into the drive matching its generation (barcode suffix L6/L9), waits until the drive is ready, and leaves it loaded. Host-side mtx/mt, bypasses P5. Refuses if P5 has a running job or a drive is loaded, unless force. 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": {
      "slot": "<slot>"
    },
    "name": "tape_load"
  }
}

Input Schema

NameRequiredDescriptionDefault
slotYesSlot number, e.g. 4
forceNoOverride the busy-library check
confirmNoMust be true to actually run

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the host-side mtx/mt mechanism, that it bypasses P5, the blocking conditions and force override, the confirm gate, and that the tape is left loaded. It omits failure/timeout behavior and what is returned when the drive never becomes ready.

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 dense passage that front-loads the action and target, then the side effects, then the refusal conditions and the confirm requirement. No filler sentences and no repetition of the tool name.

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 tool with no annotations and no output schema, the description covers mechanism, preconditions, overrides, and resulting state. Remaining gaps are edge-case behavior (timeouts, partial failures) rather than anything needed to decide whether and how to call it.

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: slot is tied to the generation-matching drive selection via barcode suffix, and force/confirm are framed as a busy-check override and an execution gate respectively. This clarifies intent beyond the terse schema strings.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (loads) and resource (tape in a library slot) plus the exact target selection rule (drive matching barcode suffix L6/L9) and the end state (waits until ready, leaves loaded). This is far more than a restatement of the name and lets an agent understand the operation without opening anything else.

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?

Gives clear preconditions for invocation: it refuses when P5 has a running job or a drive is already loaded, unless force is set, and requires confirm:true. It does not explicitly name the inverse tool (tape_unload) as an alternative, so it stops short of full when/when-not routing.

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