Skip to main content
Glama
translated

Lara Translate MCP Server

by translated

update_glossary

Update the name of an existing glossary in your Lara Translate account using its glossary ID and a new name.

Instructions

Updates the name of a glossary in your Lara Translate account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe glossary ID (format: gls_*, e.g., 'gls_xyz123')
nameYes

Implementation Reference

  • The handler function that executes the update_glossary tool logic. Validates input using the schema, then calls lara.glossaries.update(id, name) to rename the glossary.
    export async function updateGlossary(args: any, lara: Translator) {
      const validatedArgs = updateGlossarySchema.parse(args);
      const { id, name } = validatedArgs;
      return await lara.glossaries.update(id, name);
    }
  • Zod schema for update_glossary input validation. Requires 'id' (gls_* format, 1-255 chars) and 'name' (string, max 250 chars).
    export const updateGlossarySchema = z.object({
      id: z.string()
        .min(1)
        .max(255)
        .regex(/^gls_[a-zA-Z0-9_-]+$/, "Invalid glossary ID format")
        .describe("The glossary ID (format: gls_*, e.g., 'gls_xyz123')"),
      name: z
        .string()
        .describe("The new name for the glossary")
        .refine((name) => name.length <= 250, {
          message: "Name can't be more than 250 characters",
        }),
    });
  • src/mcp/tools.ts:60-60 (registration)
    Registration of update_glossary in the handlers record, mapping the tool name string to the handler function.
    update_glossary: updateGlossary,
  • Tool definition registration for update_glossary in the toolDefinitions array (exposed via ListTools). Includes description, input schema, and annotations.
    {
      name: "update_glossary",
      description:
        "Updates the name of a glossary in your Lara Translate account.",
      inputSchema: z.toJSONSchema(updateGlossarySchema),
      annotations: {
        title: "Rename glossary",
        readOnlyHint: false,
        destructiveHint: false,
        openWorldHint: false,
      },
    },
  • Narration helper in the narrate() function that generates a user-facing message for update_glossary results.
    case "update_glossary":
      return `Renamed glossary to "${result?.name ?? args?.name ?? ""}"`;
Behavior3/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. Description adds only that it updates the name, without additional behavioral context like return value or side effects.

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, no unnecessary words. Efficiently conveys the core action.

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?

Minimal description covers basic action but lacks details on success/failure conditions, error handling, or prerequisites. Given the simplicity, it's adequate but could be more complete.

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 has 50% parameter description coverage. Description adds meaning by stating the tool updates the name, clarifying the 'name' parameter's purpose, but does not elaborate on the id parameter beyond schema.

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 clearly states it updates the name of a glossary, with a specific verb and resource. It distinguishes from sibling tools like create_glossary 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 Guidelines2/5

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

No guidance on when to use this tool versus alternatives. Lacks context such as prerequisites (e.g., glossary must exist) or when not to use it.

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