Skip to main content
Glama
AIops-tools

io.github.AIops-tools/network-aiops

config_replace

Replace a device's full configuration with a configurable revert timer to prevent lockouts. Includes dry-run preview and credential-redacted diff.

Instructions

[WRITE] Replace the full config and commit under a revert timer. HIGH RISK.

Same commit-confirm contract as config_merge: the device reverts after revert_in seconds unless confirm_commit follows. Verify reachability first, then confirm. Check commit.safetyNet — when no timer could be armed the change is permanent on landing.

Returns diff and a backup digest; the raw pre-change config is kept in undo.db (0600) for the recorded rollback, not echoed back here. 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 previews the diff and runs the same refusal the real commit would, so the preview can never disagree with the commit.

Args: config_text: The full replacement configuration. 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 discloses: high risk, revert timer with confirm_commit requirement, permanent change if no timer, credential-redacted diff (no opt-out), backup digest, and undo.db storage. No behavioral surprises.

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 well-structured with front-loaded key info and separate sections for warnings, return values, and parameter details. Every sentence adds value, though slightly verbose with repeated warnings. Still efficient for the complexity.

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?

No output schema, but the description specifies return values (diff, backup digest) and mentions undo.db. Covers preconditions, side effects, and alternatives (config_diff, config_merge). Completely prepares the agent to use the tool correctly.

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?

Schema description coverage is 0%, but the description explains all four parameters: config_text (full replacement), revert_in (timer, default 300, 0 disables), dry_run (preview mode), and target (device name). Provides sufficient context beyond schema titles.

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 starts with '[WRITE] Replace the full config and commit under a revert timer. HIGH RISK.' which clearly states the verb (replace), resource (full config), and key behavior. It distinguishes from sibling config_merge by referencing the same commit-confirm contract while implying this is a full replacement.

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?

Explicitly mentions the commit-confirm contract, instructs to verify reachability and check commit.safetyNet for permanent changes. Guides on when to use dry_run and when to use config_diff with include_secrets=True for unredacted diffs. Provides clear when-to-use and when-not-to-use guidance.

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