Skip to main content
Glama

restore_backup

Destructive

Restores a MikroTik system backup from a specified file and triggers a reboot to apply the restored configuration.

Instructions

Restores a system backup on the MikroTik device; triggers a reboot.

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": {
      "filename": "<filename>"
    },
    "name": "restore_backup"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNo
filenameYes
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.9/5.0
Behavior3/5

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

The description adds genuinely useful behavior beyond the annotations by disclosing that the operation 'triggers a reboot' — a fact not encoded in destructiveHint=true or idempotentHint=false. However, it omits how disruptive that reboot is, whether the current configuration is fully overwritten, and whether credentials are required, leaving meaningful gaps for a destructive mutation.

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?

One front-loaded sentence with the action first and the side effect second — no filler or redundancy. It is arguably too terse for a destructive operation, but nothing written is wasted.

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 destructive, non-idempotent restore the description should cover the overwrite semantics, the reboot's impact, and the three undocumented parameters. As written, an agent knows only the action and that a reboot follows.

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

Parameters2/5

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

Schema description coverage is 0% across three parameters, so the description carries the full burden and largely fails: 'filename' is only obliquely implied by 'a system backup', and neither 'device' (target selection) nor 'password' (apparent auth credential) is mentioned at all. An agent gets no help understanding what these arguments expect.

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?

Names a specific verb and resource ('Restores a system backup') and scopes it to the MikroTik device, which is clear enough to distinguish from create_backup or backup_info. It stops short of explicitly contrasting with those siblings, so it does not reach the top of the scale.

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 guidance on when to choose this over create_backup/backup_info, no prerequisites (does the backup file need to already exist on the device?), and no stated conditions or exclusions. The agent must infer usage entirely from the verb.

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