Skip to main content
Glama
Sign In
Archiware MCP

Archiware MCP

by mnott
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

catalog_search

Find files in a P5 backup catalogue by glob or path/basename substring and return archive set, size, mtime, tar presence, and tape location details for restore planning.

Instructions

Read-only. Finds files in the catalogue by glob (* ?) or substring on path/basename. Per hit: set, path, size, mtime, tar name, whether the tar is still on disk, and where the tar is on tape (versions from P5's backup index: date, plan, volume label, barcode, location: library slot / mail slot / out of the house).

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

Input Schema

NameRequiredDescriptionDefault
setNo
limitNoDefault 20, max 500
patternYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.7/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 burden and does well: it declares the operation read-only and enumerates exactly what each hit contains, including the tape-location provenance from P5's backup index. Gaps remain around result ordering, pagination, and permission requirements, but the safety profile and output shape are disclosed.

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 constraint and the search mechanism before the return-field list, with no filler sentences. The tape-location parenthetical is dense and slightly run-on but every clause conveys real information.

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?

There is no output schema, so the description must describe return values, and it does so thoroughly down to tape volume labels and physical locations. The remaining incompleteness is the unexplained set filter and absent pagination/ordering notes on a three-parameter tool.

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 only 33%, so the description must compensate, and it does explain the most important parameter: pattern accepts glob wildcards or a substring against path/basename. However, the set parameter's meaning and accepted values are never explained, and limit is left entirely to the schema.

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 ('Finds files in the catalogue') plus the matching mechanism ('glob (* ?) or substring on path/basename'), which is far more than a restatement of the name. It does not name or distinguish itself from the sibling find_file, so an agent still has to guess which search tool to pick.

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?

Usage is implied by the pattern-matching explanation and the 'Read-only' prefix, but there is no explicit when-to-use or when-not-to-use guidance and no reference to alternatives such as find_file, catalog_sets, or inventory. The agent must infer the choice from tool names alone.

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