Skip to main content
Glama
Sign In
Archiware MCP

Archiware MCP

by mnott
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

library_arrange

Computes the minimal tape transfer moves, using free slots when needed, to reach a target slot layout; returns only the plan unless confirmed to execute.

Instructions

Computes the minimal list of mtx transfer moves (via free slots when needed) to reach slotLayout. Refuses while a drive is loaded or a P5 job runs. confirm:true runs the plan and then a P5 jukebox inventory + reconcile; without it only the plan is returned. For a dialog use library_plan/library_step instead.

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

Input Schema

NameRequiredDescriptionDefault
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

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 burden, and it does disclose refusal conditions plus a non-obvious side effect: confirm:true triggers a P5 jukebox inventory and reconcile after the moves. It does not mention the ability to override the busy check, nor whether physical moves are interruptible or reversible, which leaves some risk unstated.

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?

Four dense sentences, front-loaded with the core computation, then refusal rules, then the confirm split, then the alternative. No filler; each sentence changes what the agent would do.

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-style tool with no annotations and no output schema, the description covers refusal behavior, execution semantics, and routing. The main gaps are the undefined slotLayout input and the unmentioned force override, which an agent must discover from the schema alone.

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 the schema already documents confirm and force; the description does add the downstream reconcile consequence of confirm. However it references a 'slotLayout' target that is not a parameter in the schema, creating ambiguity about where the desired layout comes from.

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: computing the minimal list of mtx transfer moves to reach slotLayout, including the free-slot fallback. It also names the sibling pair (library_plan/library_step) that serves a different need, so the agent can distinguish it without opening a schema.

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

Usage Guidelines5/5

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

Gives explicit use conditions (refuses while a drive is loaded or a P5 job runs), the dry-run vs. execute split via confirm, and an explicit alternative for dialog-style use. An agent has everything needed to choose this tool or route elsewhere.

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