Skip to main content
Glama

pseudo_localize

Generate accented, expanded, bracketed pseudolocalized text to catch hard-coded strings, truncation, and layout breakage before translation; deterministic and CI-safe.

Instructions

Generate pseudolocalized text (accented + expanded + bracketed) to catch hard-coded strings, truncation and layout breakage before real translation. Deterministic; safe for CI.

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>"
    },
    "name": "pseudo_localize"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesSource string to pseudolocalize.
accentNoAccent letters. Default true.
bracketsNoWrap in 【】. Default true.
expansionNoExpansion ratio, e.g. 0.4 = +40%. Default 0.4.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does deliver genuinely useful behavioral facts: the output is deterministic and safe to run in CI, which tells an agent there are no side effects and results are reproducible. It does not state the return shape (a single string) or explicitly confirm no mutation of source data, leaving a small gap for an unannotated tool.

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?

Two tight sentences with the action and its transformations front-loaded and the behavioral guarantee ('Deterministic; safe for CI') placed last where it reads as a constraint. Nothing is redundant, though the parenthetical list is slightly compressed.

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 simple pure-function transformation tool with one required parameter, full schema coverage and no output schema, the description covers what it does, why, and its operational properties. Only the concrete return value (a transformed string) is left implicit.

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 coverage is 100%, so all four parameters and their defaults are already documented in structured form. The parenthetical 'accented + expanded + bracketed' loosely maps to three of the toggles but adds no syntax, range, or interaction details beyond the schema; 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?

Uses a specific verb and resource ('Generate pseudolocalized text') and describes the transformations applied (accented + expanded + bracketed) plus the underlying QA intent, which separates it from the real-translation sibling 'localize'. It stops short of naming that sibling explicitly, so the differentiation is implied rather than stated.

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?

Frames the use case clearly: run before real translation to catch hard-coded strings, truncation and layout breakage, and 'safe for CI' signals automation suitability. It gives no explicit exclusions or when-not-to-use conditions, and no sibling alternative is named.

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