Skip to main content
Glama
Sign In
Android i18n MCP Server

Android i18n MCP Server

by realskyrin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

translate_module

Keep Android translations current by detecting modified strings in a module's strings.xml via Git diff and translating them to all languages automatically.

Instructions

Detect changes in a specific module's default strings.xml using git diff and translate to all languages

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": {
      "modulePath": "<modulePath>"
    },
    "name": "translate_module"
  }
}

Input Schema

NameRequiredDescriptionDefault
modulePathYesPath to the Android module directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses use of git diff and that translation targets all languages, but does not mention side effects like file modifications, commit behavior, or prerequisites.

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?

A single direct sentence with no fluff, front-loaded with the action and resource; every word earns its place.

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 one-parameter tool with no output schema, the description adequately conveys the main behavior. It could mention side effects or error conditions, but given the simplicity it is complete enough.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers modulePath fully, but the description adds meaning by explaining that the module's default strings.xml is the target and that git diff is used, clarifying the purpose beyond the schema.

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 specific verb ('Detect... and translate') with a precise resource ('specific module's default strings.xml'), clearly distinguishing it from sibling 'translate_all_modules'.

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?

The context implies this is for a single module versus 'translate_all_modules', but it does not explicitly state when not to use it or compare with 'check_missing_languages' or 'create_and_translate_missing_languages'.

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

Deploy Server

Other Tools