Skip to main content
Glama

generate_i18n_plan

Analyzes detected hardcoded user-facing strings and produces a deterministic, reviewable i18n migration plan with translations, source code changes, and required hooks/imports—without modifying files.

Instructions

Analyze detected hardcoded user-facing strings and produce a complete, deterministic, reviewable i18n migration plan (translations, source code changes, and required hooks/imports) with zero filesystem mutations.

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": "generate_i18n_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoAlias for projectPath.
scopeNoOptional scope: file path, directory path, glob pattern, or an array of them to limit planning.
excludeNoOptional glob patterns to exclude from planning.
includeNoOptional glob patterns to include for planning.
structureNoOptional i18n structure type override ('namespaces', 'nested', or 'flat'). Auto-detected by default.
projectPathNoOptional path to the project root directory. Defaults to the current working directory.
sourceLocaleNoSource locale (e.g. 'en'). Defaults to the project's detected source locale.
targetLocalesNoTarget locales (e.g. ['fr', 'es']). Defaults to project's detected target locales.
includeAmbiguousNoWhether to include ambiguous low-confidence candidates in the plan for review.
candidateDecisionsNoOptional map of candidate ID (or text) to boolean decision (true = include as user-facing, false = skip as technical) for resolving ambiguous strings.
confidenceThresholdNoMinimum confidence score (0.0 to 1.0) below which candidates are marked for REVIEW.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.6

TDQS

A3.6/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full safety burden, and it does volunteer the most important trait: no filesystem mutations. It also discloses determinism, reviewability, and the shape of the output artifacts. It stops short of covering performance, auth, or how large projects are handled.

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

Conciseness4/5

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

A single front-loaded sentence with the action first and the guarantees last, no filler or restatement of the name. The stacked qualifiers ("complete, deterministic, reviewable") are slightly dense but each signals a real property.

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

Completeness3/5

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

For an 11-parameter tool with no output schema and no annotations, the description covers the output artifacts but not the workflow relationship to its apply/resolve siblings. An agent knows what it produces but not precisely when to reach for it versus the downstream tools.

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% across all 11 parameters, so the schema already explains path, scope, structure, locales, and thresholds. The description adds no parameter-level meaning or interaction rules (e.g. how candidateDecisions overrides confidenceThreshold), so the baseline 3 applies.

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 ("analyze... and produce") plus a concrete artifact ("i18n migration plan") and enumerates its contents (translations, source code changes, hooks/imports). That is enough to distinguish it from a mutating sibling like apply_i18n_plan, though the description never names the counterpart explicitly.

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?

"Reviewable" and "zero filesystem mutations" imply this is the dry-run step preceding an apply, but the description never says when to choose this tool over apply_i18n_plan or scan_hardcoded_texts. Usage is strongly implied rather than stated.

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