Archiware MCP

Overview Schema Source Related Servers Discussions Admin

plans

Lists all backup and archive configurations with descriptions, enabled flags, event names, and task names so you can inspect or select the right configuration.

Instructions

All backup plans (and archive plans if any) with description, enabled flag, event and task names. A plan is a backup configuration grouping tasks (what to back up) and events (when, into which pool).

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Nov 12, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does useful work by disclosing the returned fields and by noting that disabled plans are likely present (an 'enabled flag' is returned), but it says nothing about result size limits, ordering, or permissions for a potentially large enumeration.

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?

Two tight sentences: the first front-loads what is returned, the second supplies the domain definition of a plan. The parenthetical '(and archive plans if any)' is slightly vague — it doesn't say what an archive plan is or how to tell them apart — but costs little.

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 no-parameter read tool with no output schema, the description covers purpose, returned fields, and the domain meaning of 'plan', which is what an agent needs to call it. Missing only scale/cost signals for a full enumeration.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly does not invent parameter semantics.

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 the resource precisely — 'All backup plans' — and enumerates the fields returned (description, enabled flag, event and task names), so an agent knows this is a list operation. It distinguishes itself only implicitly from the singular 'plan' sibling by the word 'All'; it never names the alternative.

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 rather than stated: 'All backup plans' signals an enumeration call, which is enough to infer you use it to survey existing plans. There is no explicit when-to-use, no guidance on choosing between this and 'plan' or 'catalog_search', and no note on whether disabled plans are included.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server