@mcpx-digital/i18n-keys
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| compare_localesA | Compare locale files for missing/extra keys vs a base locale. Supports flat and nested keys. Local locale JSON/YAML files only — does not call translation APIs. |
| find_empty_translationsA | Find empty/null/whitespace-only translation values in locale files. Local locale JSON/YAML files only — does not call translation APIs. |
| list_keysA | List flattened keys for a single locale file. Local locale JSON/YAML files only — does not call translation APIs. |
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 3 tools
Each tool targets a clearly distinct operation: enumerating keys, diffing locales against a base, and detecting empty values. There is minimal risk of confusing one for another.
All three tools follow a strict verb_noun snake_case pattern (list_keys, compare_locales, find_empty_translations), which is predictable and readable.
Three tools is a bit thin, but the server has a narrow read-only scope over local locale files, so each tool earns its place without redundancy.
Core inspection workflows (list, compare, find empties) are covered, but there is no way to look up a single key's value or search/sort keys, leaving minor gaps an agent must work around.