verbaly
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": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| verbaly_initA | Create the config file and the locale catalogs, and detect the bundler or meta-framework so the answer names the package to add and the line to wire (what |
| verbaly_doctorA | Diagnose a Verbaly project end to end (what |
| verbaly_wrapA | Find hardcoded user-visible text in JSX/TSX files and wrap it in a t tagged template so the compiler can extract it (what |
| verbaly_extractA | Scan the source files, add new messages to the locale catalogs and refresh the generated types (what |
| verbaly_statusA | Translation coverage of the Verbaly project as numbers per locale: total messages, translated, machine translations awaiting review (drafts), broken, and translations written for an older source text (outdated). It scans the source like verbaly_extract but writes nothing. Read-only. For the entries behind the numbers, use verbaly_missing (what is missing or broken) or verbaly_drafts (each draft with its source text). |
| verbaly_missingA | The gate |
| verbaly_translateA | Fill missing translations with the configured provider (what |
| verbaly_write_draftsA | Save translations you wrote yourself, so neither a catalog nor the state file is ever edited by hand. Each one is checked the way verbaly_translate checks a provider (params, rich tags and plural cases must survive), written only for keys the source catalog has, and marked as a draft awaiting human review. Existing translations are kept unless overwrite is set, which is how an outdated one gets rewritten. Approving is not a tool here: a human reads the drafts (verbaly_drafts lists them) and runs |
| verbaly_draftsA | Every machine translation still waiting for a human, each with the source text and what the provider wrote, so a person can read both and decide. Read-only. Approving is deliberately not a tool here and never will be: a machine translation is unreviewed by definition, so accepting one is |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| verbaly-config | The resolved Verbaly config: source locale, every locale, the catalog directory and where the language lives in the url. Read this before reasoning about anything else in the project. |
| en catalog | Every message of one locale, keyed the way the runtime sees them: a nested catalog arrives flattened, a text the code owns reads as the code has it, and an empty value means untranslated. This is the only way to read what a message actually says. |
TDQS
Scored across 9 tools
Each tool targets a distinct lifecycle step (init, extract, wrap, translate, write_drafts, missing, drafts, status, doctor), but the read-only reporting trio (status/missing/drafts) and the write side (translate vs write_drafts) sit close together. The descriptions do explicitly delimit them ('for counts use verbaly_status', 'to save translations you wrote yourself, verbaly_write_drafts'), so an agent can separate them, but it takes careful reading.
Every tool uses the same verbaly_<verb/verb_noun> snake_case convention (translate, write_drafts, extract, wrap, init, doctor, missing, drafts, status). The prefix and casing are uniform throughout with no deviations.
Nine tools map cleanly onto the CLI's commands and each earns its place: one per lifecycle stage plus three focused read-only diagnostics. The set is well within the ideal 3-15 range and nothing looks redundant at the command level.
The surface covers setup (init), source handling (extract, wrap), translation generation (translate, write_drafts), and full read-only insight (status, missing, drafts, doctor). The one deliberate gap is approval/review: machine drafts can only be accepted via `verbaly review --approve` outside the tools, which is an intentional human-in-the-loop dead end rather than an oversight.