Skip to main content
Glama

commit_safe_mode

Commits pending Safe Mode changes to persistent storage and exits Safe Mode, saving router configuration edits made during a safe session.

Instructions

Commits all pending Safe Mode changes to persistent storage and exits Safe Mode.

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": "commit_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 declare readOnly=false, destructive=false and idempotent=false, and the description adds genuinely new context: the commit applies to ALL pending changes, persists them, and terminates the Safe Mode session. It does not state whether committing is irreversible or what happens if no changes are pending, but the core state transition is disclosed.

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 primary action and ending with the side effect of leaving Safe Mode. 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?

The tool is a single-action state transition and an output schema exists, so return values need not be explained. The only meaningful gap is the undocumented device parameter, which matters for multi-device usage.

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. An agent cannot learn from either source whether omitting device targets a default router or all routers.

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?

Specific verb plus resource plus outcome: commits pending Safe Mode changes to persistent storage and exits Safe Mode. The 'exits Safe Mode' clause naturally distinguishes it from rollback_safe_mode and enable_safe_mode, 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 only implied by the effect ('commits pending changes') - an agent can infer you call it to keep changes rather than discard them. There is no explicit when-to-use statement and no mention of rollback_safe_mode as the alternative for abandoning changes.

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