Skip to main content
Glama
Sign In
Archiware MCP

Archiware MCP

by mnott
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

label_tapes

Label new or empty tapes in specified jukebox slots for a pool; this overwrites slot contents, so use only on blank volumes and set confirm:true.

Instructions

DESTRUCTIVE: labels media in a jukebox's slots for a pool — this OVERWRITES the tapes in the given slots, destroying any data on them. Only new/empty volumes can be labeled. 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": {
      "jukebox": "<jukebox>",
      "pool": "<pool>",
      "slotIds": "<slotIds>"
    },
    "name": "label_tapes"
  }
}

Input Schema

NameRequiredDescriptionDefault
poolYesPool name to label for
driveNoForce this drive device (e.g. sg6): other drives get cleaning=1 during the job, restored afterwards
confirmNoMust be true to actually run
jukeboxYesJukebox name, e.g. from status
slotIdsYesSlot numbers to label, e.g. ["1","5"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.2/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 so: it discloses that the operation is destructive, that it OVERWRITES tapes in the given slots, that data on them is destroyed, and that confirm:true is mandatory. It omits the side effect on other drives (cleaning=1 during the job), though the schema covers that.

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?

Front-loads 'DESTRUCTIVE' and the overwrite warning before any procedural detail, in two tight sentences with no filler. Capitalization is used purposefully to flag risk.

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 destructive, five-parameter tool with no annotations and no output schema, the definition covers the essential safety facts: destruction, overwrite, empty-volume precondition, and confirm requirement. Return-value behavior is not described, but no output schema exists and the critical risk information is present.

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 description coverage is 100%, so every parameter is already documented, including confirm, drive, and slotIds. The description adds only the confirm:true enforcement and the constraint tying slotIds to empty volumes, which is a marginal gain over the schema.

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 and resource — labeling media/tapes in a jukebox's slots for a pool — plus a scope qualifier ('Only new/empty volumes'). This distinguishes it from adjacent operations like drive cleaning or slot inspection without needing the schema.

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 a clear applicability condition: only new/empty volumes can be labeled, so an agent knows not to run this on tapes holding data. It does not name alternative tools or explicitly exclude related operations, but the precondition is stated plainly.

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