Skip to main content
Glama
AIops-tools

io.github.AIops-tools/network-aiops

config_merge

Merge a configuration snippet under a device-side revert timer, enabling automatic rollback if management connectivity is lost. Use confirm_commit to make permanent.

Instructions

[WRITE] Merge a config snippet and commit under a device-side revert timer.

The device REVERTS the change by itself after revert_in seconds unless confirm_commit follows — so a change that severs your own management access heals without anyone having to reach the box. Verify reachability, THEN call confirm_commit. Check commit.safetyNet in the result: drivers that cannot arm a timer commit permanently and say so in commit.warning.

Returns diff and a backup digest (size + sha256). The full config is deliberately NOT returned — it carries credential hashes and PSKs — but the raw text is retained in undo.db for the recorded rollback. The diff is credential-redacted with no opt-out (see the redaction block); use config_diff(include_secrets=True) first if you must verify a literal key.

dry_run=True stages the candidate, returns the diff, discards it, and runs the SAME refusal the real commit would — so a green preview is never followed by a refusal.

Args: config_text: The configuration snippet to merge. revert_in: Device-side revert timer in seconds (default 300). 0 disables it, leaving the recorded undo as the only rollback path. dry_run: If True, preview the diff + safety assessment without committing. target: Device name from config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetNo
dry_runNo
revert_inNo
config_textYes
Behavior5/5

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

With no annotations, the description fully carries the burden of disclosing behaviors. It explains the revert timer, credential redaction (no opt-out), dry_run behavior (same refusal as real commit), non-return of full config for security, and the possibility of permanent commits with a warning. All important traits are covered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is detailed and meticulously structured, but every sentence delivers value. It opens with the primary purpose, then details behavior, workflow, and parameters. While not extremely concise, it earns its length through density of useful information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity and lack of output schema, the description is comprehensive. It covers return values (diff, backup digest), security warnings, proper workflow (dry_run -> verify -> confirm_commit), and output fields (commit.safetyNet, commit.warning). No critical information appears missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema description coverage is 0%, the description adds rich semantic meaning to each parameter: config_text (snippet), revert_in (timer behavior, default, zero disables), dry_run (preview mode), and target (device name). It explains effects and defaults beyond the schema's basic types.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's action: 'Merge a config snippet and commit under a device-side revert timer.' It specifies the verb (merge) and resource (config on device), and distinguishes itself from siblings by highlighting the revert timer mechanism, a unique feature not present in other config tools.

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

Usage Guidelines5/5

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

The description explicitly advises when to use the tool: after verifying reachability and before calling confirm_commit. It also provides guidance on when not to use it (e.g., if literal secrets are needed, use config_diff first) and explains the dry_run feature as a safe preview.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AIops-tools/Network-AIops'

If you have feedback or need assistance with the MCP directory API, please join our Discord server