Skip to main content
Glama
Sign In
Archiware MCP

Archiware MCP

by mnott
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

tape_export

Moves a tape from its slot to the first free mail slot and runs a P5 inventory, returning only a dry plan unless confirmed.

Instructions

Moves a tape (barcode or volume label) from its slot to the first free mail slot, then a P5 inventory. Same busy refusals as other tape tools. Dry plan without confirm.

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": {
      "tape": "<tape>"
    },
    "name": "tape_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
tapeYesBarcode or P5 volume label
forceNoOverride the busy-library check
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

B3.4/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 does disclose meaningful behavior: a physical move to the first free mail slot, a triggered P5 inventory afterwards, busy-library refusals, and a non-destructive dry-plan default. It omits what happens when no mail slot is free, whether the move is reversible, and any permission or operator-interaction requirements.

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?

Three short sentences, front-loaded with the core action and with no filler. The telegraphed phrasing ('then a P5 inventory', 'Same busy refusals') is dense to the point of jargon but does not waste space.

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 mutation tool with no annotations and no output schema, the definition covers the main side effects and the dry-run safety path. It still leaves notable gaps around failure modes (no free mail slot, library offline) and what the plan/commands output looks like when confirm is absent.

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%, so tape, force and confirm are already documented in the input schema, and the description largely restates them ('barcode or volume label', 'Dry plan without confirm'). The only added nuance is that the destination is the *first free* mail slot, chosen server-side rather than by parameter — a minor but genuine semantic addition.

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 a tape ... from its slot to the first free mail slot') plus a follow-on action (P5 inventory), which implicitly separates it from tape_load/tape_import. It never names a sibling to route against explicitly, so differentiation is by mechanism rather than by direct comparison.

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?

Provides one real usage rule — dry plan unless confirm is set — and a cross-reference ('Same busy refusals as other tape tools'). It does not say when to choose export over tape_unload or tape_import, nor what prerequisites (library online, mail slots available) must hold.

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