Skip to main content
Glama

localize

Translate source text into target locales and run linting plus glossary checks on results; if no compatible provider is configured, return structured translation jobs instead of fabricated output.

Instructions

Translate source text into one or more locales and post-process (lint + glossary). With an OpenAI-compatible provider configured it returns real translations; otherwise it returns structured translation jobs (it never fabricates output).

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

Input Schema

NameRequiredDescriptionDefault
textYesSource text (can be multiple lines).
localesYesTarget locales, e.g. ['de-DE','ja-JP'].
glossaryNoOptional glossary for post-check.
maxLengthNoOptional UI character budget.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/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 disclose the most important behavioral trait: a dual-mode return depending on whether an OpenAI-compatible provider is configured, plus the guarantee that it never fabricates output. It stops short of saying whether the call has side effects, what the job objects look like, or any rate/credential constraints beyond the provider requirement.

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?

Two sentences, no filler, with the core action stated first and the important provider-dependent behavior immediately after. The parenthetical "(lint + glossary)" and "(it never fabricates output)" each earn their space.

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 four-parameter tool with no annotations and no output schema, the description must explain return values itself; it only gestures at "real translations" vs. "structured translation jobs" without describing either shape. Combined with silence on glossary and maxLength effects, an agent can call it correctly but cannot anticipate what comes back.

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% with all four parameters documented (text, locales with an example, glossary, maxLength), so the schema already does the work and the description adds nothing parameter-specific. Baseline 3 is appropriate; it neither compensates for nor undermines the schema.

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?

"Translate source text into one or more locales" is a specific verb+resource, and the post-processing clause (lint + glossary) narrows the scope further. It does not explicitly distinguish itself from siblings i18n_lint or glossary_apply, so an agent must infer that this tool bundles those steps rather than replacing 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?

The description gives a conditional on outcomes (provider configured vs. not), which implies when the tool is useful, but offers no explicit when-to-use/when-not guidance and never names an alternative such as pseudo_localize for placeholder testing or i18n_lint for lint-only checks. Guidance is inferable rather than stated.

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