Skip to main content
Glama

netmiko.send_show_command_to_group

Run a CLI show command concurrently on all devices in a group, with pre-validation to reject invalid commands before any connection. Returns per-device output.

Instructions

Run the same show command concurrently on every device of a group.

IMPORTANT: If the user message involves network devices, call netmiko.get_metadata FIRST.

The command is validated once before any connection is opened, so a denied command reaches no device at all. Per-device failures are returned per device: a partial result is normal and must be reported as partial, never summarised as if every device answered.

A GROUP MAY MIX PLATFORMS. The same command string is sent to every member, so a group holding both Cisco IOS and Huawei VRP devices will fail on half of them whatever you send — show version is invalid on VRP, display version is invalid on IOS. Check device_type across the group with netmiko.list_devices first; if the group is heterogeneous, issue one netmiko.send_show_command per platform instead of forcing a single string onto all of them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandYesFull, un-abbreviated CLI command.
save_outputNoSave per-device output to disk and return filenames.
use_textfsmNoParse each output into structured JSON where possible.
device_or_groupYesGroup name (netmiko.list_groups) or a single device name.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations provided, the description fully discloses concurrent execution, pre-validation of commands, per-device failure reporting, and the platform heterogeneity risk. No contradictions with structured data.

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?

Well-structured with clear sections, important warnings highlighted, and logical flow. Slightly lengthy but every sentence serves a purpose; could be slightly more concise without losing clarity.

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?

Covers all critical aspects: concurrent execution, validation, partial failure reporting, platform heterogeneity, and prerequisites. Output schema exists so return values are not needed. Sufficient for a complex tool.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds value beyond schema by explaining that the command is validated once before connections and warns about platform mixing for the 'command' parameter. It also reinforces the meaning of 'device_or_group' as linking to list_groups/list_devices.

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 'Run the same show command concurrently on every device of a group.' It specifies the verb (run), resource (show command), and scope (concurrently on every device of a group). This distinguishes it from sibling tool 'netmiko.send_show_command' which targets a single device.

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 guidance: call netmiko.get_metadata FIRST when involving network devices, and warns against using with heterogeneous groups—directing to use send_show_command per platform instead. Also explains validation behavior and partial failure handling.

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/escrimaglia/netmiko-sot_mcp'

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