Skip to main content
Glama
Sign In
Archiware MCP

Archiware MCP

by mnott
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

restore_lookup

Look up paths, sizes, and volumes held by a backup volume or backup job to identify the correct volume ID before running a restore.

Instructions

Read-only. Lists the entries (path, size, volumes) held by a BACKUP volume, or by the volumes of a backup job, via Volume/Job inventory. Use it to find the volume id for restore.

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

Input Schema

NameRequiredDescriptionDefault
jobNoBackup job id (numeric); alternative to volume
volumeNoVolume id (numeric)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations supplied, the description correctly carries the safety burden by stating 'Read-only' up front and by enumerating the returned fields. It says nothing about permissions, result size, or whether exactly one of job/volume is required, so gaps remain beyond the one safety claim.

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, each doing distinct work: safety, behavior/output shape, and usage. The safety note is front-loaded and there is no filler.

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 two-parameter read-only lookup with no output schema, the description supplies the scope, the safety profile, and the returned fields an agent needs. It only lacks detail on whether job and volume are mutually exclusive or how results are ordered.

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 both parameters are already documented, and the description only echoes the volume-vs-job alternative already present in the schema. It adds the useful framing that job means 'the volumes of a backup job,' but gives no format or mutual-exclusivity detail beyond that.

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?

Uses a specific verb ('Lists') plus the exact resource (entries held by a BACKUP volume, or by the volumes of a backup job) and even names the returned fields (path, size, volumes). It stops short of naming a sibling it is not, so a 5 is not warranted, but the purpose is unambiguous.

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?

'Use it to find the volume id for `restore`' gives a concrete selection trigger tied to a named downstream tool. It offers no explicit when-not guidance or exclusion against other inventory-style siblings, which keeps it at a 4.

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