Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
I18N_LOCALES_DIRNoPath to the locales directory. If not set, falls back to <cwd>/config/locales.

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
localesA

List locales with file/key counts and parse problems.

keysA

List translation key paths; filter by locale and/or prefix.

get_keyA

Get a key's values across locales, with the file each lives in.

searchB

Substring search over translation keys (optionally values).

set_keyA

Create or update a key per locale. Writes to the key's current file, the nearest prefix's file, or the locale default. Warns on %{placeholder} mismatch.

delete_keyA

Delete a key from locales (default: all); prunes empty parents.

missingA

Audit keys: missing per locale, empty values, %{placeholder} mismatches vs base locale (default: en).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 7 tools

Disambiguation5/5

Each tool has a clear, distinct role: listing locales, listing keys, fetching a specific key, searching, setting, deleting, and auditing. No two tools appear to do the same thing.

Naming Consistency5/5

Tool names follow a consistent, predictable pattern: plural nouns for listing actions (keys, locales), and verb_noun for operations (get_key, set_key, delete_key). The one outlier, 'missing', is still clear as an audit verb.

Tool Count5/5

Seven tools is a well-scoped count for an i18n management server, covering the essential operations without bloat.

Completeness5/5

The toolset provides full lifecycle coverage for translation keys: read (keys, get_key, search), write (set_key), delete (delete_key), and audit (missing, locales). Minor operations like rename/move are possible via set+delete, so no dead ends.

Maintenance

ActivitySlowing
ResponsivenessNo issues