Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
explain_commandA

Explain any shell command offline: a plain-English, token-by-token breakdown of the program, its flags and operands — including pipes, redirects, subshells and common inline languages (sed/awk/jq) — plus a risk assessment. Use it to understand what a command line does before running or recommending it.

check_command_safetyA

Safety-check a shell command BEFORE executing it. Returns a risk verdict (danger / caution / none) and plain-English warnings for destructive patterns: rm -rf /, curl | sudo bash, dd/mkfs/shred/wipefs to a disk device, chmod -R 777 /, git push --force, truncating /etc/passwd, fork bombs, kill -9 -1, find / -delete, and more. Ideal as a guard an AI agent calls before running shell commands.

lint_scriptA

Safety-scan a WHOLE shell script (multi-line text) BEFORE writing or running it. Runs the same offline danger engine as check_command_safety over every logical line (comments/shebangs stripped, backslash-continuations joined) and returns each destructive or risky command with its line number: rm -rf /, curl | sudo bash, dd/mkfs/shred to a device, chmod -R 777 /, git push --force, CI ${{ }}-injection sinks, and more. Ideal for an AI agent to pre-scan a script it just generated before saving or executing it.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.3/5.0

Scored across 3 tools

Disambiguation3/5

lint_script and check_command_safety overlap substantially because both safety-scan shell content using the same danger engine; their main differentiator is whole-script vs single-command scope, which descriptions do clarify. explain_command is clearly distinct.

Naming Consistency5/5

All three tools follow a consistent lowercase verb_noun snake_case pattern: lint_script, check_command_safety, explain_command. No mixed conventions or vague placeholder names exist.

Tool Count5/5

Three tools is small but well-scoped for a focused shell safety/explanation utility. Each tool serves a distinct role: whole-script linting, single-command guarding, and command explanation.

Completeness5/5

For the stated domain of shell command safety, the surface covers the necessary workflows: pre-scanning scripts, checking individual commands before execution, and explaining commands. No obvious dead ends or critical missing operations are apparent.

Maintenance

ActivityMaintained
ResponsivenessResponsive