Skip to main content
Glama

generate_pseudolocale

Create pseudo-localized catalogs from a source locale to stress-test UI layouts, text expansion, font glyph support, and reveal unextracted strings.

Instructions

Generates pseudo-localized catalogs (e.g. qps-ploc, en-XA) from the source locale for stress-testing UI layouts, text expansion (+35%), font glyph support, and spotting unextracted strings.

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_pseudolocale"
  }
}

Input Schema

NameRequiredDescriptionDefault
dryRunNoIf true, simulates generation and returns diffs without modifying files. If false, writes catalogs to disk.
strategyNoPseudo-localization strategy: 'accented' (diacritics), 'bidi' (RTL mirroring), 'expansion' (text elongation), or 'all' (default).all
delimiterNoSurrounding delimiters: 'exclamation' ([!! ... !!]), 'brackets' ([...]), or 'none'.exclamation
namespacesNoOptional list of namespaces to limit pseudo-localization to.
projectPathNoOptional project root directory. Defaults to current working directory.
sourceLocaleNoSource locale to read from (e.g. 'en'). Defaults to project source locale.
targetLocaleNoTarget pseudo-locale name (e.g. 'qps-ploc', 'en-XA', or 'qps-plocm' for bidi). Defaults to 'qps-ploc'.
expansionRatioNoLength expansion multiplier (default 0.35, i.e., +35% longer text).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.6

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies generation but does not disclose that catalogs are written to disk by default, whether existing files are overwritten, permission or project-root requirements, or how dryRun changes behavior beyond what the schema says.

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?

The description is a single front-loaded sentence that states the action, examples, and intended uses with no unnecessary wording. Every clause contributes either purpose or usage context.

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?

The purpose and main use cases are complete enough for an agent to understand the tool, and the schema richly documents all eight optional parameters. However, for a file-generating tool with no annotations and no output schema, the description should say more about side effects, overwrite behavior, and what is produced versus only simulated.

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 the input schema already explains all eight parameters in detail. The description adds useful context around the +35% expansion example and pseudo-locale names, but it does not add syntax or semantics beyond the schema for parameters such as strategy, delimiter, namespaces, or dryRun.

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 and resource: 'Generates pseudo-localized catalogs' with examples qps-ploc and en-XA. It is clearly distinguishable from siblings by the pseudo-localization resource, but it does not explicitly name an alternative sibling or state when another i18n generation tool should be used instead.

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

Usage Guidelines4/5

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

It gives clear usage contexts: stress-testing UI layouts, text expansion, font glyph support, and spotting unextracted strings. This is more than implied usage, but it does not include exclusions or explicitly route the agent toward or away from sibling tools.

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