DialectOS
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| translate_markdownB | Translate a markdown file while preserving structure (code blocks, links, etc.) |
| extract_translatableA | Extract translatable text from a markdown file (excludes code blocks, HTML) |
| translate_api_docsB | Translate API documentation markdown with optimized handling for tables and lists |
| create_bilingual_docB | Create a side-by-side bilingual document with original and translated sections |
| detect_missing_keysB | Compare two locale files and report missing keys |
| translate_missing_keysB | Translate missing keys from base locale to target locale |
| batch_translate_localesC | Translate base locale to multiple target dialects |
| manage_dialect_variantsB | Create dialect-specific variants of a locale file |
| check_formalityC | Check locale file for formality consistency |
| apply_gender_neutralB | Apply gender-neutral language strategies to a locale file |
| translate_textB | Translate text to a Spanish dialect |
| detect_dialectB | Detect Spanish dialect from text using keyword matching |
| translate_code_commentC | Extract and translate code comments (basic text extraction) |
| translate_readmeB | Translate a README markdown file preserving structure |
| search_glossaryB | Search the built-in glossary for technical and business terms |
| list_dialectsA | List all 20 Spanish dialects with metadata |
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 16 tools
Most tools have clearly distinct purposes, but there is some potential overlap among translate_markdown, translate_readme, and translate_api_docs; descriptions alleviate confusion slightly.
All tools follow the verb_noun pattern in snake_case, making naming fully consistent and predictable.
16 tools is well-scoped for a dialect translation server, covering translation, detection, management, and glossary without being excessive.
The tool set covers core translation, detection, and locale management needs, but could include a direct validation or export tool for full completeness.