Skip to main content
Glama

vyos_validate

Validate VyOS configuration syntax by temporarily applying commands for 1 minute and rolling back automatically. Ensures syntax correctness without persisting changes.

Instructions

Validate VyOS configuration syntax without persisting changes.

Applies commands with a 1-minute commit-confirm window and does NOT
confirm, so the router automatically rolls back. This is not a true
dry-run — the configuration is temporarily applied for up to 1 minute.

A successful response means the syntax is valid. An error means the
commands contain invalid syntax or paths.

Args:
    commands: List of config operations, each with 'op'
        ('set'/'delete') and 'path' (list of strings).
        Example: [{"op": "set", "path": ["firewall",
        "group", "network-group", "MY_GROUP"]}]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandsYes
Behavior5/5

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

With no annotations, the description fully discloses the temporary application of configuration, auto-rollback after 1 minute, and the meaning of success/error responses. This provides essential behavioral context beyond the bare input schema.

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?

The description is concise, using few sentences to convey the purpose, behavior, and parameter format. It includes a clear Args section and example, making it easy to parse without verbosity.

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 lack of output schema and annotations, the description covers all necessary aspects: validation goal, temporary application, error interpretation, and parameter specification. It is fully sufficient for an agent to understand and use the tool.

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?

The input schema only defines the 'commands' parameter as an array of objects with additionalProperties true, providing minimal semantic meaning. The description compensates by specifying the required structure (op and path fields) and giving a concrete example, which is critical for correct invocation.

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?

Description clearly states the tool validates VyOS configuration syntax without persisting changes, and distinguishes itself from a true dry-run by noting temporary application and auto-rollback. This specificity helps differentiate it from sibling tools like vyos_configure.

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

Usage Guidelines4/5

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

The description explains the validation context and the behavior (1-minute commit-confirm window, auto-rollback), which guides when to use the tool. It does not explicitly list when not to use or compare to alternatives, but the purpose is clear enough.

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/cacack/mcp-server-vyos'

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