Skip to main content
Glama
translated

Lara Translate MCP Server

by translated

list_languages

Read-only

Retrieve the full list of languages supported by your Lara Translate account. Identify available translation languages for your projects.

Instructions

Lists all supported languages in your Lara Translate account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual handler function for list_languages. Calls lara.getLanguages() to retrieve supported languages.
    export async function listLanguages(lara: Translator) {
      return await lara.getLanguages();
    }
  • Input schema definition for list_languages. Empty object since this tool takes no arguments.
    export const listLanguagesSchema = z.object({});
  • src/mcp/tools.ts:70-74 (registration)
    Registration of listLanguages in the 'listers' record, mapping the tool name to its handler function.
    const listers: Record<string, Lister> = {
      list_memories: listMemories,
      list_languages: listLanguages,
      list_glossaries: listGlossaries,
    };
  • Tool definition registration with name, description, inputSchema, and annotations for the list_languages tool.
    {
      name: "list_languages",
      description:
        "Lists all supported languages in your Lara Translate account.",
      inputSchema: z.toJSONSchema(listLanguagesSchema),
      annotations: {
        title: "List supported languages",
        readOnlyHint: true,
        destructiveHint: false,
        openWorldHint: false,
      },
    },
  • Dispatch logic in CallTool(). list_languages is invoked via the 'listers' path since it's not in handlers.
    } else if (name in listers) {
      result = await listers[name as keyof typeof listers](lara);
    } else {
      logger.warn(`Requested a tool with name ${name}, but it was not found`);
      throw new InvalidInputError(`Tool ${name} not found`);
    }
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds no behavioral context beyond this, such as rate limits or auth needs, so it meets the baseline.

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?

One concise sentence that is front-loaded with the key action and resource. No wasted words.

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

Completeness5/5

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

Given zero parameters, no output schema, and annotations covering safety, the description is complete. It adequately defines the tool's function.

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?

There are no parameters in the schema, so the baseline is 4. The description does not need to add parameter information, as none exist.

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 clearly states the verb 'lists' and the resource 'all supported languages in your Lara Translate account'. It distinguishes from sibling tools, as no other tool lists languages.

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 is provided on when to use this tool versus alternatives. There is no mention of context, exclusions, or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/translated/lara-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server