Skip to main content
Glama
Sign In
Archiware MCP

Archiware MCP

by mnott
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

dryrun_plan

Starts a safe dry-run job for a backup plan, scanning and reporting potential actions without writing data or requiring confirmation.

Instructions

Starts a dry-run job for a backup plan (safe: scans and reports, writes nothing). No confirm needed.

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": {
      "id": "<id>"
    },
    "name": "dryrun_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPlan id

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 zero annotations, the description carries full burden and does disclose two useful traits: no writes occur and no confirmation step is required. It omits what happens after the job starts, whether a job identifier is returned, and how to track the run (presumably via the job sibling).

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?

Two short sentences with the core action front-loaded and the safety qualifier immediately after in parentheses. No wasted wording.

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 one-parameter tool with no output schema, the definition supplies what's needed to call it safely: the resource, the id, and the non-destructive guarantee. The only gap is how the resulting job is observed afterward, which a brief pointer to the job tool would fix.

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?

A single required 'id' parameter with 100% schema description coverage, so the schema already labels it 'Plan id'. The description adds nothing about the parameter but there is essentially nothing to add for one field; baseline 4 applies.

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 names a specific verb and resource: 'Starts a dry-run job for a backup plan.' The 'dry-run' qualifier effectively sets this apart from an actual plan start, though it never names start_plan explicitly as the contrasting sibling.

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?

'safe: scans and reports, writes nothing' and 'No confirm needed' imply when you'd reach for this over a real start, but the description never states the alternative or an explicit when-not condition. Usage must be inferred from the safety note.

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