Skip to main content
Glama
Sign In
Archiware MCP

Archiware MCP

by mnott
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

library_step

Executes one confirm-gated step of a tape-library session, re-checking busy state and slot contents first, then returns the outcome and next instruction, including verified human tape steps.

Instructions

Executes exactly one next step of a session (confirm-gated) and returns what happened plus the next instruction, including human steps (put/take a tape at the mail slot; those are verified, not executed). Re-checks busy state and slot contents first and stops if reality differs from the plan. The last step runs the P5 inventory and reconcile.

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": {
      "session": "<session>"
    },
    "name": "library_step"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoOverride the busy-library check
confirmNoMust be true to actually run; without it only the plan/commands are returned
sessionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.8/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 behavioral burden and does well: it discloses precondition re-checks (busy state, slot contents), a stop condition when reality diverges from plan, and that human steps are verified rather than executed. It does not mention permissions or side effects of the underlying step, which keeps it from a 5.

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 tight sentences, front-loaded with the core action, with no filler. The parenthetical about human steps is worth its space but makes the middle sentence slightly dense.

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?

No output schema exists, yet the description states what comes back (what happened plus the next instruction) and notes the terminal step runs P5 inventory and reconcile. Little is missing for an agent to call it correctly, aside from the undocumented session parameter.

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?

Schema coverage is 67%, with 'session' undocumented, but the description adds real meaning: 'confirm-gated' explains the confirm flag's role and 're-checks busy state' explains what force overrides. It goes beyond the schema's terse field descriptions.

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 specific verb and resource: executes exactly one next step of a session, and returns the outcome plus the next instruction. This distinguishes it from a planning tool, but it never names a sibling such as library_plan to make the split explicit.

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?

The confirm gate ('Must be true to actually run') and the one-step-at-a-time cadence imply a dry-run/first, execute/later usage, but the description never states when to prefer library_plan or when this tool is wrong to call. Usage is inferable rather than prescribed.

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