Skip to main content
Glama
ellmos-codecommander-mcp

ellmos-codecommander-mcp

cc_set_language

Sets the output language for CodeCommander tools using a language code, ensuring results appear in the selected language.

Instructions

Set the output language for CodeCommander tools

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": {
      "language": "<language>"
    },
    "name": "cc_set_language"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageYesLanguage code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.27
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / language / enum
      Previous value: -[
      -  "de",
      -  "en",
      -  "es",
      -  "zh",
      -  "ja",
      -  "ru"
      -]New value: +[
      +  "de",
      +  "en",
      +  "es",
      +  "zh",
      +  "ja",
      +  "ru",
      +  "fr",
      +  "hi",
      +  "ar",
      +  "bn",
      +  "pt"
      +]
  2. Changed1 schema field changedv1.3.16
    • changedInput schema / properties / language / enum
      Previous value: -[
      -  "de",
      -  "en"
      -]New value: +[
      +  "de",
      +  "en",
      +  "es",
      +  "zh",
      +  "ja",
      +  "ru"
      +]
  3. First observedv1.3.8

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It doesn't say whether the setting persists across sessions, applies only to subsequent calls, is scoped per-connection, or what happens on success. For a global state-mutating tool this is a meaningful gap.

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?

One short sentence, front-loaded with verb and object, no filler. It is efficient, though it is arguably too terse given the behavioral disclosure gap.

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

Completeness3/5

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

A simple one-parameter tool with no output schema keeps the bar low, and the enum makes the input unambiguous. However, the persistence and scope-of-effect semantics that matter for a global language switch are absent.

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% and the single parameter is an enum of 11 language codes documented as 'Language code', so the schema does the heavy lifting. The description adds nothing beyond it, which is the baseline 3 case.

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?

States a specific verb and resource: 'Set the output language for CodeCommander tools'. The scope (all CodeCommander tools) is clear. It doesn't explicitly name cc_get_language as the counterpart reader, but the set/get pairing is inferable from the sibling name.

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

Usage Guidelines3/5

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

Usage is implied rather than stated — an agent can infer this is the tool to call when output language must change, but there is no explicit when-to-use, when-not-to-use, or reference to cc_get_language for reading the current setting.

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