Skip to main content
Glama

nohup

Destructive

Execute commands immune to SIGHUP, enabling long-running background tasks to persist after terminal exit. Captures output to a file.

Instructions

Run a command immune to SIGHUP (hangup signals), ideal for long-running background tasks. Executes the given command and captures stdout/stderr. Requires --allow_nohup confirmation for safety. Use to run tasks that should survive terminal closure. Not for CPU priority adjustment — use 'nice'. Not for time-bounded execution — use 'timeout'. See also 'nice', 'timeout'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
allow_backgroundNoAllow starting a real background process.
allow_overwriteNoAllow replacing an existing output file.
appendNoAppend to the output file.
command_argsNoCommand and arguments to run.
dry_runNoReport without starting a process.
outputNoOutput file for stdout/stderr.nohup.out
parentsNoCreate missing output parent directories.
Behavior4/5

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

Annotations already set destructiveHint=true. Description adds context about executing commands and capturing output, but could detail destructive implications further. No contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three focused sentences with clear front-loading of core functionality, plus explicit alternatives. No fluff.

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

Completeness4/5

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

Covers main use, alternatives, and safety requirement. Schema provides parameter details. Missing information about error handling or return format, but acceptable for a simple tool.

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

Parameters2/5

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

Description references a non-existent '--allow_nohup' parameter, misleading the agent. Schema covers all parameters (100%), but the description injects confusion.

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?

Clearly states it runs commands immune to SIGHUP, capturing stdout/stderr. Distinguishes from siblings by naming 'nice' and 'timeout' as alternatives for different purposes.

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?

Explicitly says when to use (survive terminal closure) and when not to (CPU priority, time-bounded). Also mentions required confirmation flag.

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/caseSHY/AI-CLI'

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