Skip to main content
Glama
Archiware MCP

Archiware MCP

by mnott

slots

Retrieves per-position tape-library details, including barcode, P5 volume label/pool/state, unknown-volume flag, and drive load status, to support inventory checks.

Instructions

Per-slot view of the tape library: slot number, barcode (from mtx), and P5 volume id/label/pool/mode/state if known, with an unknownToP5 flag; drive loaded state from mtx. A volume is one piece of media P5 identifies by a label written at its beginning.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

Without annotations, the description carries the full burden. It discloses the returned fields and the unknownToP5 flag, which is useful, but it does not explicitly state that the operation is read-only, mention any required permissions, or describe side effects. The read-only nature is strongly implied by 'view' but not stated.

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?

The description is two sentences and front-loads the core purpose ('Per-slot view of the tape library'). The second sentence about what a volume is adds helpful context, though it could be considered slightly extraneous. Overall it is clear and appropriately sized.

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 zero-parameter, read-only listing tool with no output schema, the description is fairly complete: it explains what fields are returned and clarifies the unknownToP5 flag. It does not cover pagination, error conditions, or permissions, but those may be less critical for a simple slot view.

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?

The tool has zero parameters, so the baseline is 4. The description adds no parameter information because none exist; the schema coverage is 100% for an empty parameter set.

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 clearly states it provides a per-slot view of the tape library, listing specific fields (slot number, barcode, P5 volume id/label/pool/mode/state, unknownToP5 flag, drive loaded state). It is a specific verb+resource, but it does not differentiate itself from sibling tools like inventory or health.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given on when to use this tool versus alternatives (e.g., inventory, health, or catalog tools). The description implies it is for viewing slot details, but it does not state any conditions, prerequisites, or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.