Kotlin Multi-Agent Orchestrator

Overview Schema Source Related Servers Discussions Admin

generate_kotlin_localization

Generates Android strings.xml resource bundles for en, es, and ar (RTL) locales and creates Jetpack Compose AppStrings type-safe helpers.

Instructions

Generates Android strings.xml resource bundles (values, values-es, values-ar for RTL) and Jetpack Compose AppStrings type-safe helpers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "generate_kotlin_localization"
  }
}

Input Schema

Name	Required	Description	Default
`stringKeys`	No	Map of string keys to translations.
`defaultLocale`	No		en
`supportedLocales`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 30, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose the generated outputs (strings.xml bundles and Compose AppStrings helpers), including the RTL note for Arabic, but it omits side effects such as file creation, overwriting behavior, or project integration requirements.

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?

The description is a single, front-loaded sentence with no filler. It states the tool's output and key locale detail efficiently.

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

Completeness2/5

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

Given there is no output schema and no annotations, the description should explain how parameters affect generation, what files are written, and what the agent can expect back. It only covers the general output shape, leaving locale configuration, default locale behavior, and invocation results underspecified.

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

Parameters2/5

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

Schema description coverage is only 33percent; the description does not describe defaultLocale or supportedLocales semantics or how they map to the generated bundles. It hints at en/es/ar locales through values, values-es, values-ar, but does not compensate for the undocumented parameters.

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 uses a specific verb ('Generates') and names concrete resources: Android strings.xml bundles for values, values-es, values-ar and Jetpack Compose AppStrings helpers. This clearly distinguishes it from sibling tools like generate_kotlin_api_bridge or scaffold_kotlin_database.

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?

There is no guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. The description implies Android localization work, but never says explicitly when an agent should choose this over other Kotlin generation tools.

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