Skip to main content
Glama

i18n_lint

Lint translated strings against locale rules for separators, punctuation, RTL bidi marks, placeholder parity, and length limits to catch localization defects before release.

Instructions

Lint a translated string against a locale's rules: number/date separators, quote style, CJK fullwidth punctuation, RTL bidi marks, placeholder parity with source, and length budget. Deterministic.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>",
      "locale": "<locale>"
    },
    "name": "i18n_lint"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesTranslated string to check.
localeYesTarget locale, e.g. de-DE. See list_locales.
sourceNoOptional source string for placeholder parity check.
maxLengthNoOptional UI character budget.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations exist, so the description must carry the full behavioral burden. 'Deterministic' is a genuinely useful disclosure implying a pure, repeatable, side-effect-free check, but the description never states that nothing is mutated, nor describes the shape of the result (pass/fail vs. a findings list with severities and positions). For a diagnostic tool with no annotations and no output schema, that leaves real gaps.

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?

One front-loaded sentence carrying the verb, scope, and check list, plus a single-word 'Deterministic.' qualifier. Every clause adds information about what is validated; nothing is redundant or buried.

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

Completeness4/5

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

For a four-parameter, non-mutating lint tool with fully described schema fields, the definition covers purpose and check scope well. The remaining shortfall is the absence of any statement about what the tool returns or how failures are surfaced, which matters given there is no output schema and no annotations.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, and the description earns extra credit by explaining the role of the optional parameters: placeholder parity clarifies why 'source' matters, and 'length budget' clarifies maxLength. The enum-less locale format is only handled via 'e.g. de-DE' in the schema itself, so a little meaning is still left implicit.

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

Purpose5/5

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

The description opens with a specific verb+resource ('Lint a translated string against a locale's rules') and then enumerates the exact checks performed: separators, quote style, CJK fullwidth punctuation, RTL bidi marks, placeholder parity, and length budget. This makes it clearly a check-only tool, distinguishable from transform-oriented siblings like localize or pseudo_localize without needing to name them.

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 noun 'lint' and the check list; there is no explicit statement of when to run it (pre-ship validation, CI gating) or when not to. The only routing hint is the schema-level pointer to list_locales for locale values, which is not guidance about choosing this tool over siblings.

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