Skip to main content
Glama

rollback_safe_mode

DestructiveIdempotent

Discard pending Safe Mode changes by closing the SSH session, triggering automatic rollback and restoring the MikroTik device's prior configuration.

Instructions

Discards all pending Safe Mode changes by closing the SSH session, triggering automatic rollback.

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

Input Schema

NameRequiredDescriptionDefault
deviceNo

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

A3.6/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and idempotentHint=true, so safety is covered. The description adds genuinely new mechanism detail beyond the structured fields: that rollback occurs via closing the SSH session and is triggered automatically, which tells the agent the connection will be severed as a side effect.

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?

One sentence, front-loaded with the action, with zero filler. The mechanism clause adds value rather than padding.

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 one-parameter destructive tool with annotations covering safety and an output schema covering returns, the description is nearly complete. The remaining gap is the unexplained 'device' parameter and the absence of a note on what state the device is left in after rollback.

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?

The single 'device' parameter has 0% schema description coverage and is never mentioned in the description, so an agent gets no guidance on whether omitting it targets the default/current device or whether it selects which device's session is rolled back. With low coverage the description is expected to compensate, and it does not.

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 uses a specific verb ('Discards') plus resource ('all pending Safe Mode changes'), which contrasts implicitly with the paired commit operation in the sibling list. An agent can tell this is the rollback/discard path rather than the commit path, though no sibling is named explicitly.

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?

Usage is implied by 'Discards all pending Safe Mode changes' — an agent can infer this is for abandoning uncommitted work — but there is no explicit when-to-use, no mention of prerequisites (Safe Mode being enabled), and no named alternative such as commit_safe_mode.

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