Skip to main content
Glama
dwin-gharibi

ArvanCloud MCP Server

by dwin-gharibi

arvan_ssh_run

Execute a shell command on a remote server via SSH and retrieve its exit status, standard output, and standard error.

Instructions

Run a single command on a server over SSH and return its output.

Args: host: Server IP or hostname (e.g. a freshly created server's public IP). command: The shell command to execute. username: SSH user (defaults to ARVAN_SSH_USER, typically root). port: SSH port (default 22). private_key: Inline PEM private key (overrides the configured default). key_file: Path to a private key file. password: Password auth (if not using a key). passphrase: Passphrase for an encrypted private key. known_hosts: Path to a known_hosts file; omit to skip host-key checks. connect_timeout: Seconds to wait for the connection. command_timeout: Seconds to wait for the command to finish.

Returns: {exit_status, stdout, stderr, host}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostYes
commandYes
usernameNo
portNo
private_keyNo
key_fileNo
passwordNo
passphraseNo
known_hostsNo
connect_timeoutNo
command_timeoutNo
Behavior4/5

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

Annotations (readOnlyHint=false, destructiveHint=false) are vague; description compensates by detailing connection and authentication options (e.g., known_hosts skipping host-key checks, default username, timeouts). However, it does not disclose potential side effects or resource consumption.

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 Args and Returns sections, each line adds value. Slightly verbose (14 lines) but no unnecessary content. Could be tightened, e.g., by grouping related parameters.

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 11 parameters, 2 required, no output schema, the description covers all inputs and explicitly states the return format ({exit_status, stdout, stderr, host}). No gaps in user understanding for executing a single SSH command.

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 has 0% description coverage; the description provides thorough explanations for all 11 parameters, including defaults, examples (e.g., 'a freshly created server's public IP'), and behavior (e.g., 'omit to skip host-key checks'). Fully compensates for schema deficiency.

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 'Run a single command on a server over SSH and return its output,' which is a specific verb+resource. Among siblings, there are tools for checking connections, downloading files, running scripts, and uploading files, so this tool is well-distinguished.

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

Usage Guidelines3/5

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

Description lists parameters and implicitly suggests it's for single commands, but provides no explicit guidance on when to use this tool vs siblings like arvan_ssh_run_script or arvan_ssh_download_file. Usage context is implied but not clarified.

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/dwin-gharibi/arvancloud-mcp'

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