Multilocale Translations

Add a language and translate it

add_locale

Destructive

Use this when someone asks to add a new language to a project and translate their strings into it. Returns the updated language list and how many strings were machine-translated, one per key, all before anything is saved, so a very large project can time out. Not for a language the project already has.

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": {
      "project": "<project>",
      "locale": "<locale>"
    },
    "name": "add_locale"
  }
}

Input Schema

Name	Required	Description
`model`	No	Translation model id; defaults to gpt-6-luna
`locale`	Yes	Locale code to add, such as it or pt-BR
`context`	No	Note applied to every translation in this run, up to 600 characters
`project`	Yes	Project id or name

Output Schema

Name	Required	Description	Default
`locale`	Yes
`status`	Yes
`locales`	Yes
`project`	Yes
`translationCount`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 28, 2026

changedInput schema / properties / context / description

Previous value: -"Optional context applied while translating the missing phrases."New value: +"Note applied to every translation in this run, up to 600 characters"

changedInput schema / properties / locale / description

Previous value: -"New locale code to add (for example, it)"New value: +"Locale code to add, such as it or pt-BR"

changedInput schema / properties / model / description

Previous value: -"Translation model to use. Defaults to gpt-6-luna."New value: +"Translation model id; defaults to gpt-6-luna"

changedInput schema / properties / project / description

Previous value: -"Project name (slug) to localize"New value: +"Project id or name"

Changed1 schema field changedSep 23, 2026

changedInput schema / properties / model / description

Previous value: -"Translation model to use. Defaults to gpt-5.6-luna."New value: +"Translation model to use. Defaults to gpt-6-luna."

First observedAug 30, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false. The description adds critical behavioral context beyond annotations: it specifies the return payload (language list and translation count), notes that translations occur before saving, and warns that large projects can time out. However, it doesn't elaborate on the destructive nature (e.g., what data is overwritten or affected).

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?

Three tightly packed sentences that are front-loaded with purpose and usage, then behavioral details. No wasted words; every sentence adds value.

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

Completeness5/5

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

Given the complexity (dual add+translate operation), the description covers what the tool does, when to use it, what it returns, and key caveats (timeout risk). With an output schema present, it doesn't need to detail return values. Annotations cover safety aspects. Nothing critical is missing for an agent to decide and invoke correctly.

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 parameter descriptions are in the schema. The description adds no parameter-level details beyond what the schema provides. It mentions 'language' and 'strings' generically but doesn't map to specific parameters like locale, model, or context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (add) and resource (language/locale), with the implied translation action. Distinguishes from siblings clearly - no other tool handles adding a locale. The description makes the dual nature (add + translate) explicit.

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

Usage Guidelines5/5

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

Explicitly states when to use ('when someone asks to add a new language...') and provides a clear exclusion ('Not for a language the project already has'). This prevents the agent from attempting to add an existing locale.

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

All Multilocale Translations tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?