Skip to main content
Glama
Sign In
DialectOS

DialectOS

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

batch_translate_locales

Translate a base locale file into multiple Spanish dialects using a specified provider. Supports directories of locale files and arrays of target dialect codes.

Instructions

Translate base locale to multiple target dialects

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": {
      "directory": "<directory>",
      "targets": "<targets>"
    },
    "name": "batch_translate_locales"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetsYesArray of target Spanish dialect codes
providerNoTranslation provider name (deepl, libre, mymemory)
directoryYesDirectory containing locale files
baseLocaleNoBase locale name (e.g., en, es-ES)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

The description provides minimal behavioral insight beyond stating the action. With no annotations, it should describe effects like whether files are created or modified, or if authorization is needed. The phrase 'Translate' is vague about side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, which is concise but may be too terse given the tool's 4 parameters and lacking sibling differentiation. It conveys the basic purpose but does not efficiently use space to add value.

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?

Without annotations or output schema, the description fails to cover important context such as return values, file handling behavior, or prerequisite conditions. For a batch operation, more detail is needed for correct invocation.

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 parameters have descriptions within the input schema. The description adds no additional meaning beyond what is already provided in the schema, e.g., it does not clarify the relationship between 'targets' and 'provider'.

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?

The description 'Translate base locale to multiple target dialects' clearly states the tool's action (translate) and resource (base locale to multiple target dialects). The tool name includes 'batch_translate_locales' which hints at batch processing of locale files. While it distinguishes from siblings like translate_text, it could be more explicit about targeting locale files.

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?

No guidance on when to use this tool versus alternatives such as translate_missing_keys or translate_text. The description implies usage for batch translation to multiple dialects, but lacks explicit context or when-not-to-use instructions.

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