Skip to main content
Glama

Set languages

set_languages
Idempotent

Set the learner's native language and the language they want to learn. Both as ISO code ('de') or English name ('German').

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": {
      "native": "<native>",
      "learn": "<learn>"
    },
    "name": "set_languages"
  }
}

Input Schema

NameRequiredDescriptionDefault
learnYesLanguage to learn, ISO code or English name.
nativeYesNative language: ISO code like 'de' or English name like 'German'.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the mutation profile is supplied structurally. The description's only added behavioral content is the accepted input format (ISO code or English name); it does not state whether existing settings are overwritten wholesale, whether an invalid language errors or is ignored, or whether both values must be set together.

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?

Two short sentences, front-loaded with the action and then the input format, with no filler. The second sentence largely duplicates what the schema descriptions already say, which is the only waste.

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 setter with full schema coverage, annotations, and no output schema, the description supplies everything needed to construct a call. It is slightly thin on failure modes and on the relationship to 'find_languages', but nothing essential for correct invocation is missing.

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% and both parameters are documented in the schema with the same ISO-code-or-English-name convention. The description merely restates that convention rather than adding constraints such as case sensitivity, accepted code set, or fallback behavior, so the baseline of 3 applies.

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 names a specific verb ('Set') and resource (the learner's native and target language), so the agent knows exactly what state is changed. It does not distinguish itself from 'find_languages', which is the obvious adjacent operation (discovering codes before setting them), so it falls short of a 5.

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 only implied: the agent can infer this is the write step for language configuration, but there is no explicit when-to-use framing, no prerequisite (e.g., call find_languages first to obtain a valid code), and no note on what happens if a language is unsupported. 'find_languages' exists as a sibling and is never referenced.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources