Skip to main content
Glama

run_commands

Execute network topology CLI commands (add, rename, delete, show) against a .nsm master file to modify or inspect the network state.

Instructions

Execute one or more Network Sketcher CLI commands against a .nsm master.

PREREQUISITE: You MUST have called get_ai_context(master) (or at least
get_network_state(master)) at least once in this session before using
this tool. Without that context you do not know the current state nor
the available CLI syntax, and your edits are likely to be wrong.

Each non-empty line of `commands` is parsed with shlex and run as a
single CLI invocation. Allowed verbs: add, rename, delete, show.
`export` is intentionally excluded; use create_empty_master,
export_diagram, or get_ai_context instead.

The `--master` argument is appended automatically; do NOT include it
in the command lines.

Args:
    master: Master filename inside the working directory.
    commands: Newline-separated CLI command lines. Example:
                  add device 'SW-3' --area 'DC1'
                  add l1_link 'SW-2' 'GE 0/0' 'SW-3' 'GE 0/1'

Returns:
    Per-line results: each command's exit summary and stdout, joined.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
masterYes
commandsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Describes parsing of each line with shlex, invocation as single CLI command, and automatic appending of '--master'. It lists allowed verbs (add, rename, delete, show) and excluded export. Though no annotations exist, the description covers the execution behavior well, though it lacks explicit mention of destructive potential or error handling.

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?

Description is front-loaded with purpose and prerequisite. While slightly long, each sentence adds value, and the example helps. Structured with Args and Returns sections. Could be more concise but overall efficient.

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 no annotations and the presence of an output schema, the description adequately covers input parameters, prerequisite, allowed verbs, and return format. It is fully sufficient for an 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 coverage is 0%, but the description adds full meaning: 'Master filename inside the working directory' for master, and 'Newline-separated CLI command lines' with an example for commands. This provides complete semantic understanding beyond the raw schema.

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 explicitly states 'Execute one or more Network Sketcher CLI commands against a .nsm master,' clearly specifying the verb (execute) and resource (CLI commands on .nsm master). It distinguishes from sibling tools by listing allowed verbs and explicitly excluding 'export', which directs to sibling 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?

Provides explicit prerequisites ('MUST have called get_ai_context...'), explains why the prerequisite is necessary, and gives clear when-to-use and when-not-to-use guidance by listing allowed verbs and excluding 'export'. Also warns not to include '--master' argument.

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/cisco-open/network-sketcher'

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