Skip to main content
Glama

ros_backup

Create a binary system backup on a MikroTik router and save it to the router's file system for later download, giving a restorable snapshot of the current configuration and state.

Instructions

Create a binary backup (/system backup save) on the router; download it with ros_file_download.

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

Input Schema

NameRequiredDescriptionDefault
nameNomcp-backup
routerNo
passwordNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses that the result is a binary backup and names the underlying CLI command, but says nothing about authentication, where the file is stored, whether an existing backup with the same name is overwritten, or how long the operation may take.

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?

The description is a single tight sentence that front-loads the action and resource, then names the natural follow-up tool. There is no redundant or filler wording.

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?

For a router mutation that creates a file and has three undocumented parameters, no annotations, and no output schema, one sentence is insufficient. An agent still lacks details about authentication, file naming and overwrite behavior, and what happens after the backup is created.

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 must compensate and does not. It does not explain the name parameter (default mcp-backup), the router selector, or the password parameter, leaving the agent to infer all parameter meaning from bare schema fields.

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 gives a specific verb and resource: create a binary backup on the router, and even names the underlying command (/system backup save). It also points to ros_file_download as the follow-up tool, though it does not distinguish this backup operation from siblings like ros_export.

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?

It implies the workflow: create the backup here, then download it with ros_file_download. However, it gives no explicit guidance on when to choose this over ros_export or other siblings, nor any prerequisites or exclusions.

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