Skip to main content
Glama

enable_safe_mode

Activates MikroTik Safe Mode so configuration changes stay in memory and auto-revert on disconnect until committed.

Instructions

Activates MikroTik Safe Mode; changes are held in memory and auto-reverted on disconnect until committed.

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": "enable_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?

Annotations only declare readOnly=false, destructive=false, idempotent=false, openWorld=false; the description goes meaningfully beyond them by explaining that changes are buffered in memory and auto-reverted on disconnect until committed. That is exactly the state-lifecycle context an agent needs. It stops short of covering repeated-invocation behavior, which matters given idempotentHint=false.

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 and followed by the behavioral consequence. No filler or redundancy.

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?

An output schema exists, so return values need no explanation, and the description adequately conveys the state semantics of a simple toggle tool. The only real hole is the unexplained 'device' parameter, which leaves target selection ambiguous.

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?

There is one parameter ('device', nullable, default null) with 0% schema description coverage, and the description never mentions it — not which device is targeted, not what the null default means (presumably the current/connected device), and not whether it's required. With low coverage the description should 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?

States a specific verb and resource ('Activates MikroTik Safe Mode') and adds the defining mechanism (in-memory changes auto-reverted on disconnect). It doesn't name the contrasting siblings commit_safe_mode or rollback_safe_mode, but the phrase 'until committed' implicitly points at the commit path, so an agent can still orient itself.

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 only implied: the description suggests this is what you do before making changes that you may want to discard, and 'until committed' gestures at commit_safe_mode. There is no explicit when-to-use, when-not-to-use, or named alternative, and nothing says what happens if safe mode is already active.

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