Skip to main content
Glama
sandbanks

Agentic_SSH

run_command

Execute shell commands on a single host or multiple hosts concurrently. Supports background execution, output abbreviation, and progress tracking for efficient SSH orchestration.

Instructions

Executes a shell command on a single host ('host') or multiple hosts concurrently ('hosts'). If using 'hosts', returns a JSON map mapping hostnames to their stdout, stderr, and exit codes. Features optional 'background' execution (starting the command and returning a local log file path immediately for async tracking), 'quiet' execution (suppressing progress logs), and output abbreviation controls. Prefer 'hosts' to execute commands across cluster nodes simultaneously.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostNoThe target hostname or IP address
hostsNoA list of hostname targets to query concurrently
quietNoIf true, suppresses terminal progress logging in background files (default: false)
commandYesThe shell command to run on target
max_linesNoMax lines to return if abbreviate is true (default: 100)
abbreviateNoIf true, limits long stdout output (default: true)
backgroundNoIf true, runs command in background and returns log path immediately (default: false)
progress_interval_secsNoNumber of seconds between progress reporting updates (default: 5)
Behavior4/5

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

Given no annotations, the description covers key behaviors: return format for multiple hosts, background execution returning log path, quiet mode, and abbreviation controls. It lacks details on error handling and security, but sufficiently describes core features.

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 concise, using a single paragraph with key information front-loaded. It could be slightly structured with bullet points, but it is efficient and clear.

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

Completeness3/5

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

The description covers most features but omits return format for single host execution and error behavior. Despite no output schema, it partially compensates by describing return for multiple hosts. Some gaps remain.

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?

With 100% schema coverage, baseline is 3. The description adds meaningful context beyond schema, explaining how 'hosts' returns a JSON map and how background, quiet, and abbreviate affect execution.

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 it executes shell commands on a single host or multiple hosts concurrently, explaining the return format for multiple hosts. It distinguishes from sibling tools by focusing on arbitrary command execution.

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 explicitly recommends using 'hosts' for cluster-wide commands, providing guidance on when to use single vs. multiple hosts. However, it does not mention when to avoid this tool in favor of sibling tools like tail_log or search_processes.

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/sandbanks/agentic_ssh'

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