Skip to main content
Glama

Skillshop

audit_backup_plan

Check a backup plan against 3-2-1 with tested restores (paid, metered).

datasets: [{name, copies: [{type: original|backup|snapshot|raid|sync, location, medium, offsite: bool, encrypted: bool, last_restore_test: 'YYYY-MM-DD'}]}]. Count the original as a copy.

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": {
      "datasets": "<datasets>"
    },
    "name": "audit_backup_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
datasetsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does add genuinely useful behavior: the check is metered/paid, it evaluates against 3-2-1 including restore-test recency. It never states read-only vs mutating, permission requirements, or what happens with malformed datasets, which for an unannotated tool is a real gap.

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?

Very short and the purpose is front-loaded before the data-shape detail. The bracketed pseudo-schema is dense and slightly hard to parse, but every fragment (cost note, type enum, counting rule) carries information rather than filler.

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

Completeness3/5

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

An output schema exists, so return values need not be explained. However, with a single deeply-nested parameter at 0% schema coverage, the terse inline notation leaves gaps: cardinality expectations, whether offsite/encryption are judged per medium, and date-format handling for last_restore_test.

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 0% and the schema is a bare array of open objects, so the description is the only source of meaning. It supplies the expected shape (name plus copies with type/location/medium/offsite/encrypted/last_restore_test), an enum for type values absent from the schema, and the counting rule 'Count the original as a copy.'

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 ('Check a backup plan') plus the exact criteria applied (3-2-1 with tested restores). That is enough for an agent to distinguish it from the sibling audit_* tools, which cover grants, handoffs, and status reports rather than backup posture.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no prerequisites (e.g. data must already be inventoried). Usage is only implied by the object of the verb. The '(paid, metered)' note warns about cost but does not route the agent between alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources