Skip to main content
Glama
Sign In
Archiware MCP

Archiware MCP

by mnott
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

library_plan

Proposes steps for an arrange, export, or import operation and returns a session ID; nothing moves until confirmed. Use simulate to test on a virtual library without hardware.

Instructions

Proposes the steps of a rearrangement (arrange), export or import and returns a persisted session id. Nothing moves until library_step. simulate:true walks the session on a virtual library without touching hardware.

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": {
      "kind": "<kind>"
    },
    "name": "library_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
tapeNoexport: barcode or label
mailSlotNo
simulateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.7/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 behavioral burden. It does disclose key behavior: planning is non-destructive until library_step, a session ID is persisted, and simulate runs virtually without touching hardware. It does not cover session lifetime, permission requirements, error conditions, or what the proposed steps look like.

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?

Three short sentences with no waste. The non-destructive constraint is front-loaded, followed by the execution dependency on library_step and the simulate option. Every sentence adds value.

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 planning tool with no output schema and no annotations, the description covers the core lifecycle entry point and the simulation mode. It is incomplete regarding session management, the relationship to abort, and two undocumented parameters, so an agent must infer too much.

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 low at 25%, and four parameters exist. The description explains the kind values (arrange, export, import) and the simulate behavior, partially compensating. It says nothing about mailSlot and only repeats the schema's own hint for tape, leaving meaningful gaps.

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 a specific verb and resource: proposing steps for arrange, export, or import and returning a persisted session ID. It distinguishes itself from library_step by saying nothing moves until that tool is called. It does not address the sibling library_arrange, whose name could be confused with the arrange kind, leaving some ambiguity.

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?

Usage is clearly implied as a two-phase flow: call library_plan first, then library_step to execute. The simulate flag is described as a dry-run alternative that walks a virtual library without hardware. It lacks explicit when-not-to-use guidance or mention of library_abort for abandoning a session.

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