Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
HTB_HOSTS_FILENoTarget hosts file (handy for testing)/etc/hosts
HTB_HOSTS_KEEPNoComma-separated domain substrings to keep outside the block on migrate
HTB_HOSTS_BACKUP_DIRNoWhere snapshots are stored~/.local/state/htb-hosts

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
htb_hosts_addA

Add or update an HTB host entry in /etc/hosts (no sudo needed). Use this whenever you need a hostname like machine.htb to resolve to a box IP. Entries go in a managed block and can be cleaned later.

htb_hosts_removeB

Remove an HTB host entry from the managed block by hostname or IP.

htb_hosts_cleanA

Remove managed host entries. No args wipes the whole block; tag removes one box by its exact tag; match removes the entries htb_hosts_select would return for the same patterns (every pattern must match); exclude is the inverse keep-list, removing everything EXCEPT entries matching ANY pattern. The three are mutually exclusive. Set dry_run to preview what would go without touching the file.

htb_hosts_showA

Structured overview of the managed hosts, both flat ('entries') and grouped by box ('groups'). patterns narrows to the entries they select, exactly as htb_hosts_select does. Set full=true to also include unmanaged/system entries (localhost, etc.).

htb_hosts_selectA

Look up managed entries by fuzzy pattern and return just their bare values, ready to feed into another command. patterns matches against ip/tag/hostname, and several patterns NARROW (every one must match). field picks what comes back: 'ip' (default) or 'host'. Use this to resolve a box name to its IP before scanning.

htb_hosts_retagA

Recompute every entry's tag from its box name (fixes bulk tag=imported).

htb_hosts_backupA

Save an explicit snapshot of /etc/hosts (never auto-pruned).

htb_hosts_restoreA

Restore /etc/hosts from a snapshot (most recent if no name is given).

htb_hosts_list_backupsA

List available /etc/hosts snapshots, oldest first.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 9 tools

Disambiguation4/5

Most tools have clearly distinct purposes: add/remove/show/select/retag/backup/restore/list_backups are easy to separate. The main overlap is between htb_hosts_remove and htb_hosts_clean, since both can remove managed entries by hostname/IP or pattern, though their descriptions clarify the difference.

Naming Consistency5/5

All tools use the same htb_hosts_ prefix and snake_case verb-based naming. The pattern is predictable throughout, including list_backups as a verb_noun variant.

Tool Count5/5

Nine tools is well-scoped for a focused /etc/hosts management server. Each tool covers a meaningful operation: entry lifecycle, querying, cleanup, tagging, and backup/restore.

Completeness5/5

The surface covers the full lifecycle: add/update, remove, patterned cleanup, structured and bare-value lookup, retagging, snapshot creation, restore, and backup listing. No obvious operations are missing for managing a managed hosts block.

Maintenance

ActivityMaintained
ResponsivenessNo issues