Skip to main content
Glama

Download a configuration backup

backup_config
Read-only

Saves the router startup configuration to a backups directory with owner-only permissions, creating a known-good state to return to before making changes.

Instructions

Saves the router startup configuration into this tool's backups directory (KEENETIC_STATE_DIR/backups) with owner-only file permissions. Take one before any sequence of changes so there is a known-good state to return to. Reading the configuration changes nothing on the router.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.3
    • removedInput schema / properties / path
      Removed value: -{
      -  "description": "Absolute path of the local file to write.",
      -  "type": "string"
      -}
    • removedInput schema / required
      Removed value: -[
      -  "path"
      -]
  2. First observedv0.0.0-dev

TDQS

A4.3/5.0
Behavior5/5

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

With only readOnlyHint=true supplied, the description adds exactly the context an agent needs: the operation writes a local file into KEENETIC_STATE_DIR/backups, applies owner-only permissions, and explicitly clarifies that 'Reading the configuration changes nothing on the router.' That resolves the apparent tension between a file-writing tool and a readOnly annotation rather than contradicting it.

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?

Three short sentences: destination and file semantics first, then the recommended usage, then the no-side-effect reassurance. No sentence is redundant and the most decision-relevant fact is front-loaded.

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 zero-parameter tool with no output schema, the definition covers purpose, side effects, and timing well. The one remaining gap is what the caller gets back (e.g., the backup file path or identifier), which matters here precisely because no output schema exists to describe it.

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; baseline applies. The description correctly avoids inventing arguments and instead spends its words on behavior.

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 a specific verb and resource ('Saves the router startup configuration') and states the destination ('this tool's backups directory (KEENETIC_STATE_DIR/backups)'), which is far more specific than the title alone. It does not explicitly contrast itself with the similarly named save_config sibling, so an agent must infer that distinction from the directory path.

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

Usage Guidelines4/5

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

It gives clear situational guidance: 'Take one before any sequence of changes so there is a known-good state to return to.' That is a concrete precondition an agent can act on. It stops short of naming an alternative (e.g., save_config) or a when-not-to-use case, so it is strong but not exhaustive.

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