Skip to main content
Glama

Pseudo-localize UI copy

bpj_pseudo_locale_preview
Read-onlyIdempotent

Accent English vowels and expand text length for UI testing, preserving simple braced arguments.

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

Input Schema

NameRequiredDescriptionDefault
textYes
growthYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered externally. The description's one addition beyond that is valuable and non-obvious: braced arguments are preserved, not accented or expanded. It stays silent on what the output looks like and on how the growth factor is applied (uniform per-character vs. padding).

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 transformation first and the preservation caveat last; no filler. It is arguably too terse for a 0%-coverage schema, but the sentence itself earns its place.

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 a simple two-parameter, non-destructive, annotation-rich tool with no output schema, the description covers the core transformation and placeholder preservation. The remaining gaps are growth semantics and output shape, which matter because the schema titles alone do not tell an agent how to choose a growth value.

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 0%, so both parameters ('text' and 'growth') depend on the description or on their titles. The description implies 'text' is the source string and 'growth' controls expansion magnitude, but never states that growth is a percentage, that it is bounded 0-100, or that text is capped at 6000 characters. It also leaves 'simple braced arguments' undefined as a syntax constraint.

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 names a specific verb pair ('Accent English vowels and expand text length') and the target resource ('text ... for UI testing'), so an agent knows this produces pseudo-localized copy rather than a real translation. It does not distinguish itself from preview siblings such as bpj_visible_whitespace_preview or bpj_markdown_first_preview, which keeps it below a 5.

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

Usage Guidelines2/5

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

'For UI testing' hints at the scenario but gives no explicit when-to-use, exclusions, or alternatives (e.g., when to use this instead of another preview tool or a real locale mock). The agent must infer applicability from the purpose clause alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.