Skip to main content
Glama
Sign In
Archiware MCP

Archiware MCP

by mnott
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

tape_import

Imports a tape from the mail slot into its pool’s target or first free slot, then runs a P5 inventory; without confirm, returns only a dry-run plan.

Instructions

Moves the tape in a mail slot to the target slot of its pool per slotLayout (else the first free slot), then a P5 inventory. Dry plan without confirm.

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

Input Schema

NameRequiredDescriptionDefault
forceNoOverride the busy-library check
confirmNoMust be true to actually run; without it only the plan/commands are returned
mailSlotNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.7/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 disclose non-obvious behavior: the target slot is computed, a P5 inventory is run afterwards as a side effect, and the operation is dry-run by default without confirm. It omits failure modes and what happens if the pool is full or the library is busy (that only appears in the schema for 'force').

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 dense sentences, front-loaded with the action and slot rule, then the side effect and the dry-run default. Nothing is wasted, though the jargon ('P5 inventory', 'slotLayout') assumes domain familiarity.

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 mutation tool with no annotations and no output schema, the description covers the essential flow: what moves, where it goes, the follow-up inventory, and the confirm gate. Remaining gaps are error/edge behavior and confirmation of what the dry-run returns, which the schema partially covers.

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 67%, so the schema documents 'force' and 'confirm' but leaves 'mailSlot' as a bare name. The description reinforces the confirm/dry-run semantics and the slot-selection logic, but does not explain the mailSlot domain (valid range, physical slot numbering) or what 'slotLayout' refers to.

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 concrete verb and resource ('Moves the tape in a mail slot') plus the destination rule (pool slot per slotLayout, else first free slot), which is specific enough to distinguish it from the sibling tape_load/tape_unload operations. It stops short of explicitly naming those siblings as alternatives.

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 final clause 'Dry plan without confirm' implies the safe-preview workflow before committing, which is useful usage guidance. However, there is no explicit statement of when to choose this over tape_load or tape_unload, and no prerequisites such as the library needing to be idle.

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