Unix Manual Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_command_documentationC | Get documentation for a command in Unix-like system. Args: command: The command to get documentation for (no arguments) prefer_economic: Whether to prefer the economic approach (--help/-h/help) [default: True] man_section: Specific manual section to look in (1-9) [optional] Returns: The command documentation as a string |
| list_common_commandsB | List common Unix commands available on the system. Returns: A list of common Unix commands |
| check_command_existsC | Check if a command exists on the system. Args: command: The command to check Returns: Information about whether the command exists |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: checking command existence, retrieving documentation, and listing common commands. There is no overlap in functionality, making it easy for an agent to select the appropriate tool without confusion.
The tools follow a consistent verb_noun pattern (check_command_exists, get_command_documentation, list_common_commands), with minor deviations in verb choice ('check', 'get', 'list'). The naming is predictable and readable, though not perfectly uniform in verb style.
With only 3 tools, the server feels thin for a Unix manual domain, which might include operations like searching commands, filtering by category, or managing documentation. While the core functions are covered, the toolset could benefit from additional utilities to enhance completeness.
The tools cover the essential operations for a Unix manual server: verifying command availability, fetching documentation, and listing commands. Minor gaps exist, such as the inability to search or filter commands, but agents can work around these limitations with the provided tools.