Skip to main content
Glama
translated

Lara Translate MCP Server

by translated

create_glossary

Create a glossary with a custom name to enforce specific terminology during translations in your Lara Translate account.

Instructions

Create a glossary with a custom name in your Lara Translate account. Glossaries enforce specific terminology during translation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes

Implementation Reference

  • The main handler function that executes the create_glossary tool logic. It validates the input args using the schema, extracts the name, and calls lara.glossaries.create(name).
    export async function createGlossary(args: any, lara: Translator) {
      const validatedArgs = createGlossarySchema.parse(args);
      const { name } = validatedArgs;
      return await lara.glossaries.create(name);
    }
  • Input schema for create_glossary using Zod. Defines a 'name' field with a maximum length of 250 characters and a descriptive prompt.
    export const createGlossarySchema = z.object({
      name: z
        .string()
        .describe(
          "The name of the new glossary, it should be short and descriptive, like 'brand_terms' or 'legal_terminology'"
        )
        .refine((name) => name.length <= 250, {
          message: "Name of the glossary can't be more than 250 characters",
        }),
    });
  • src/mcp/tools.ts:59-59 (registration)
    Registration of the createGlossary function in the handlers record, mapping the tool name 'create_glossary' to its handler.
    create_glossary: createGlossary,
  • Tool definition/registration with name, description, inputSchema, and annotations for the MCP protocol.
    {
      name: "create_glossary",
      description:
        "Create a glossary with a custom name in your Lara Translate account. Glossaries enforce specific terminology during translation.",
      inputSchema: z.toJSONSchema(createGlossarySchema),
  • Response formatting helper for the create_glossary tool, producing a human-readable success message.
    case "create_glossary":
      return `Created glossary "${result?.name ?? args?.name ?? ""}"`;
Behavior3/5

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

Annotations already indicate a non-read-only write operation; description adds that it creates a resource in the user's account. No additional behavioral traits like idempotency or limits are disclosed.

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?

Two sentences, no wasted words, front-loaded with action and purpose. Every word adds value.

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?

Covers the basic purpose and parameter of a simple creation tool, but lacks return value description and does not mention naming uniqueness or constraints. Adequate with gaps.

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?

With 0% schema description coverage, the description calls the name 'custom' which adds minimal context but does not specify constraints like uniqueness or format. Partially compensates for schema gaps.

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?

Clearly states the tool creates a glossary with a custom name, and contextualizes it by explaining glossaries enforce specific terminology. This distinguishes it from siblings like add_glossary_entry or delete_glossary.

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

Usage Guidelines4/5

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

Implies usage for enforcing terminology during translation, but does not explicitly state when to use versus alternatives like update_glossary or when not to use. Lacks exclusion criteria.

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