Skip to main content
Glama

owa_tran

Translate English UI labels into the language the app is currently displaying, so you can name on-screen controls correctly in your own guides and instructions.

Instructions

What a button is CALLED on this user’s screen when the app runs in another language: pass the English label as the manual writes it, get back the words printed on that control, and name it with those. Help pages, guide cards and tool answers already come back translated -- this is only for a label you wrote yourself. A label the app does not translate comes back in English, as it is on screen.

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": "owa_tran"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoA language code; default the language the app is showing.
textYesThe English label, exactly as the manual writes it (e.g. "Clear Slide"). A list translates several at once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and usefully discloses the untranslated fallback: labels the app does not translate come back in English. It does not explicitly state read-only behavior or error handling, but for a simple lookup the key behavioral trait is covered.

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?

The definition is only three sentences and is front-loaded with the purpose, followed by scope and fallback. The first sentence is a little convoluted with the colon and all-caps emphasis, but there is no filler.

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 two-parameter translation lookup with no output schema, the description covers the main purpose, scope, and fallback behavior. It leaves the array-return shape and failure modes implicit, but not enough to prevent correct use.

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%, including the exact-label requirement and the optional language code, so the baseline is 3. The description reinforces the exact English-label expectation but adds little parameter meaning beyond what the schema already provides.

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?

The description states a concrete job—taking an English UI-control label and returning the localized text—and distinguishes it from already-translated content. An agent can tell it is a label-translation lookup rather than a general translation or language-setting tool.

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 explicitly excludes help pages, guide cards, and tool answers because those are already translated, and limits use to labels the caller wrote. A positive trigger is implied rather than stated and no alternative tool is named, so it falls short of a 5.

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