Skip to main content
Glama
Sign In
Archiware MCP

Archiware MCP

by mnott
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

find_file

Search file names across all backups to list every version and everywhere it can be restored from, ordered by cheapest source: disk, tape library, or offline tape.

Instructions

Read-only. Searches file NAMES (substring, or glob with * ?; a pattern with / also matches the directory) across all backups: the P5 backup index copy (needs index_sync) and the tar catalogue. Returns every matching file (full path) with every version (distinct mtime+size, newest first); each version lists all places it can be fetched from, cheapest first: 1 disk-tar (inside a tar still on disk, no tape needed), 2 tape-library (P5 volume in the library) or tar-on-tape in library, 3 tape-offline (only on tapes outside the library: shows the barcode to insert). Same path+mtime+size from several sources is one version with several locations. Each version has a key and each location an id for restore_version.

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": {
      "pattern": "<pattern>"
    },
    "name": "find_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNomax files, default 20, max 200
sinceNoonly versions modified on/after YYYY-MM-DD
underNoonly below this directory (path prefix)
clientNoonly this P5 client
patternYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations supplied, the description carries the full burden and does so: it declares read-only, discloses the two-index search scope, result ordering ('newest first'), version deduplication ('same path+mtime+size ... is one version'), and the cheapest-first priority scheme with numbered tiers explaining what each location class means. It also explains that tape-offline results surface a barcode to insert, which is real operational context an agent could not infer.

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?

Front-loaded with the read-only flag and the search target, and every clause carries information (matching rules, index prerequisites, ordering, location tiers). It is dense to the point of being a single long block, and the priority enumeration could be easier to scan, but there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five parameters, no output schema, and no annotations, the description compensates by fully specifying the return shape: full paths, versions with distinct mtime+size, ordered locations, version keys and location ids. An agent has everything needed to call it and to chain into restore_version.

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 80%, so the schema already documents limit, since, under, and client. The description goes beyond it for the one undocumented parameter, 'pattern', by defining substring vs. glob syntax and the '/'-matches-directory rule. It adds little for the remaining parameters, so it is strong but not fully additive.

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 ('Searches file NAMES') plus the exact scope: both the P5 backup index copy and the tar catalogue. It also pins down matching semantics (substring, glob with * ?, '/' matching directory), which distinguishes this from a catalogue-wide or task-oriented search without 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?

It gives a concrete prerequisite ('the P5 backup index copy (needs index_sync)') and a downstream handoff ('each location an id for restore_version'), so an agent knows how to enable the index path and where to go next. It stops short of explicit when-not-to-use guidance or naming a sibling to prefer for other search shapes.

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