codex-hermes-worker
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_workspace_filesC | List bounded file metadata under an allowed read root. |
| read_text_excerptA | Read a bounded UTF-8 text chunk; use offset_chars to continue a large file. |
| get_file_metadataC | Return deterministic size, hash, magic, extension, MIME guess, and entropy. |
| read_binary_sliceB | Read one bounded binary slice as hexadecimal. |
| extract_printable_stringsB | Extract bounded ASCII strings from a file without invoking a model. |
| search_file_namesB | Find bounded filename matches; query may be text or a glob such as *.json. |
| search_textB | Search one allowed text file or all eligible files below an allowed directory. |
| run_ffprobeC | Run the fixed ffprobe metadata command on an allowed input path. |
| query_mock_functionA | Query one test pseudocode record by address; never modifies a disassembler DB. |
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 9 tools
Each tool maps to a clearly distinct operation: listing, reading text, reading binary, extracting strings, metadata, filename search, content search, ffprobe, and function-record query. Potential overlaps like list_workspace_files vs get_file_metadata are separated by scope (directory-level vs file-level detail).
All tool names follow a consistent snake_case verb-first pattern such as list_, read_, get_, extract_, search_, run_, and query_. The object is always the target resource, and there are no mixed conventions or vague verbs.
Nine tools is a well-scoped size for a read-only file/workspace inspection server. Each tool provides a distinct capability without redundancy, and the count is neither bloated nor too thin.
The read-only surface is broadly complete: listing, text and binary reads, metadata, strings, filename/content search, media probing, and function-record lookup are all covered. The main minor gap is the lack of a binary-content search, though bounded slices and string extraction provide workarounds.