bluente-translate

Official

Overview Schema Source Related Servers Discussions Admin

bluente_get_supported_languages

List all available language pairs for translation on the Bluente platform to determine which languages can be translated.

Instructions

List all language pairs currently supported by the Bluente translation platform.

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": "bluente_get_supported_languages"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Implementation Reference

src/tools/get-supported-languages.tool.js:5-12 (registration)

The MCP tool 'bluente_get_supported_languages' is registered here. The handler executes client.getSupportedLanguages().

export function registerGetSupportedLanguagesTool(server, { client }) {
  server.tool(
    TOOL_NAME,
    "List all language pairs currently supported by the Bluente translation platform.",
    {},
    async () => executeTool(TOOL_NAME, async () => client.getSupportedLanguages())
  );
}

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Mar 28, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. It fails to disclose safety characteristics (read-only vs destructive), return format, pagination behavior, or what 'language pairs' specifically refers to (e.g., ISO codes vs full names). Only the scope 'all' is clarified.

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?

Single sentence of 10 words with no redundancy. Information is front-loaded and every word earns its place. Appropriate length for a parameterless discovery endpoint.

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?

Without an output schema, the description should ideally explain the return structure (e.g., array of language codes). While 'language pairs' gives a hint, the lack of format details or example values leaves a gap for a tool whose only purpose is to return data.

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?

Tool has zero parameters and schema coverage is 100% (vacuously true). Per scoring rules, 0 parameters establishes a baseline of 4. The description correctly implies no filtering is possible by stating 'List all'.

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?

Description provides specific verb 'List', clear resource 'language pairs', and scope 'Bluente translation platform'. It clearly distinguishes this discovery tool from operational siblings like upload_file or translate_document_workflow.

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 explicit guidance on when to use this tool versus alternatives, or prerequisites for calling it. While the purpose is clear, the description does not state that this should be called before translating to verify language availability.

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

Deploy Server