stylesync
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STYLESYNC_BASE_GGUF | No | Override the path to the base GGUF model file. | |
| STYLESYNC_LLAMA_URL | No | Override the URL of the shared llama-server backend (default: http://127.0.0.1:18080). | |
| STYLESYNC_LORA_GGUF | No | Override the path to the LoRA GGUF adapter file. | |
| STYLESYNC_MODEL_DIR | No | Override the model directory where the base and LoRA GGUF files live (default: platformdirs.user_cache_dir("stylesync"), e.g. ~/Library/Caches/stylesync on macOS). | |
| STYLESYNC_LLAMA_SERVER | No | Path to the llama-server (llama.cpp) binary, e.g. /opt/homebrew/bin/llama-server. Needed when the app's PATH lacks Homebrew. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rewrite_styleA | Rewrite a neutral Vietnamese draft into the owner's own voice (casual, abbreviations, Gen Z). |
| healthA | Report the local llama-server backend: reachable, stylesync adapter loaded, model files, last latency. |
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 2 tools
The two tools have clearly distinct purposes: rewrite_style transforms text into the owner's voice, while health reports backend status. There is no realistic overlap or risk of misselection between them.
rewrite_style follows a clear verb_noun snake_case pattern, while health is a standalone noun. This is a minor deviation, but the meaning remains obvious and predictable.
The surface is very narrow: one core transformation tool plus a health check. Two tools is borderline thin, though it may be appropriate for a tightly scoped style-rewriting backend.
The core rewrite operation covers message, commit, and comment use cases with guard and warning feedback, and health covers backend visibility. Minor gaps remain around style configuration or inspecting the owner profile, but core workflows are covered.