Remove directories on remote servers via SSH. Supports recursive deletion and sudo for elevated access.
Remove a directory on the remote system.
Returns: Dictionary with operation status
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Directory path to remove | |
| use_sudo | No | Use sudo for the operation | |
| recursive | No | Remove directory and contents recursively |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. Fails to disclose behavior on non-existent directories, permission requirements, or side effects beyond operation status.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, no wasted words. Could be slightly more structured (e.g., bulleted parameter notes) but acceptable.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No annotations; output schema exists but description doesn't explain return dictionary keys. Does not mention that recursive is required for non-empty directories.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so baseline is 3. Description adds no extra parameter meaning beyond what's in schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states verb 'remove' and resource 'directory on the remote system'. Distinguishes from siblings like ssh_dir_delete and ssh_dir_batch_delete_files.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool vs alternatives (e.g., ssh_dir_delete, ssh_dir_batch_delete_files). No context on prerequisites or typical use cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/cygnussystems/cygnus-ssh-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server