Skip to main content
Glama

validate_i18n

Validate i18n catalogs to detect missing translations, interpolation mismatches, orphan or unused keys, and malformed JSON before release.

Instructions

Validate i18n implementation for missing translations, interpolation variable mismatches, orphan keys, unused dead keys, and malformed JSON.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "validate_i18n"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeNoOptional specific directory or file scope when checkSourceCode or checkUnusedKeys is enabled.
localesNoOptional list of locales to validate against the source locale.
namespacesNoOptional list of namespaces to validate.
projectPathNoOptional project root directory. Defaults to current working directory.
checkSourceCodeNoIf true, also scans source files for remaining unextracted hardcoded strings.
checkUnusedKeysNoIf true, scans source code to identify dead/unused keys in locale catalogs.
pruneUnusedKeysNoIf true, safely deletes unused/dead keys from all locale catalogs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.6

TDQS

B3.2/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the full behavioral burden, and it omits the most important trait: with pruneUnusedKeys=true this tool deletes keys from locale catalogs, a destructive mutation that the description never discloses. It also says nothing about preconditions (a source locale must exist), whether fixes are applied automatically, or what the result contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that opens with the verb and resource and spends the rest on a tight enumeration of checks. No filler, no repetition of the tool name or schema content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a seven-parameter tool with zero annotation coverage and no output schema, the description is too thin: it never warns that pruneUnusedKeys mutates catalogs, never states that all parameters are optional with conservative defaults, and never describes what a validation report looks like.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so each of the seven parameters is already documented in the schema, which sets the baseline at 3. The description's mention of missing translations, orphan keys, unused keys and malformed JSON loosely maps to checkUnusedKeys/checkSourceCode, but adds no format, default, or interaction detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb+resource ("Validate i18n implementation") and enumerates the exact checks performed: missing translations, interpolation variable mismatches, orphan keys, unused dead keys, malformed JSON. An agent can tell this apart from translate_i18n or internationalize, though it does not explicitly name any sibling as an alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the enumerated check types: an agent can infer it should call this when it wants a whole-catalog validation pass. There is no explicit when-to-use, when-not-to-use, or routing guidance such as using audit_plurals or audit_rtl for the narrower checks those siblings appear to cover.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.