Skip to main content
Glama
zibdie
by zibdie

ssh_execute

Run commands on remote servers via established SSH connections, with configurable timeout and connection selection.

Instructions

Execute a command on an established SSH connection

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandYesCommand to execute on the remote server
connectionIdNoConnection ID to usedefault
timeoutNoCommand timeout in milliseconds
Behavior2/5

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

No annotations provided, so the description must carry the full burden. It fails to disclose what happens on connection failure, output handling, or timeout behavior.

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?

Single sentence is concise and front-loaded. However, it could include more context without being verbose.

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

Completeness2/5

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

Despite low complexity, the description omits critical information about return values, error handling, and execution details. It is too minimal.

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

Parameters3/5

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

Schema coverage is 100%, with each parameter described. The description adds no extra meaning beyond the schema, which is acceptable per baseline scoring guidelines.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action 'Execute' and the resource 'a command on an established SSH connection'. It distinguishes from siblings like ssh_connect and ssh_disconnect, though ssh_execute_script is similar but not identical.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. Does not mention that a connection must be established first via ssh_connect, nor contrasts with ssh_execute_script.

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/zibdie/SSH-MCP-Server'

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