Skip to main content
Glama

create_backup

Creates a system backup on a MikroTik device, letting you save configuration and optional sensitive data with custom name, comment, and encryption settings.

Instructions

Creates a system backup on the MikroTik device.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
deviceNo
commentNo
dont_encryptNo
include_passwordNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.14.5
    • addedInput schema / properties / device
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Device"
      +}
  2. First observedv0.0.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already disclose that this is a non-read-only, non-destructive, non-idempotent write, and the description adds nothing beyond that. It does not say where the backup file is stored, whether an existing file of the same name is overwritten, or that repeated calls create separate backups (consistent with idempotentHint=false but not explained).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero padding, which is structurally sound. The problem is under-specification rather than verbosity: the one sentence does not carry enough information for a 5-parameter mutation tool.

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

Completeness2/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, but for a backup-creation tool with 0% schema coverage the description should cover file placement, naming defaults, and the encryption/password options. None of that is present, leaving the agent to call a security-relevant write operation blind.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 5 parameters, and the description mentions none of them. The most consequential ones — dont_encrypt and especially include_password, which defaults to true — are security-sensitive and completely unexplained, so the description provides no meaning beyond the raw 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?

The description states a specific verb and resource ("Creates a system backup") and names the target platform (MikroTik device), so the core action is unambiguous. It does not, however, distinguish this from siblings like create_export or backup_info, leaving the agent to infer whether a binary backup or a text export is produced.

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 when-to-use guidance, no prerequisites, and no mention of the obvious alternatives (restore_backup for restoring, backup_info for inspecting, create_export for a config export). The agent must guess which backup-related tool fits its intent.

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