Skip to main content
Glama
translated

Lara Translate MCP Server

by translated

delete_glossary

Destructive

Remove a glossary from your Lara Translate account using its unique ID. Permanently delete glossaries to manage your translation resources.

Instructions

Deletes a glossary from your Lara Translate account.

Input Schema

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

Implementation Reference

  • The actual handler function for the delete_glossary tool. Validates args using deleteGlossarySchema and calls lara.glossaries.delete(id).
    export async function deleteGlossary(args: any, lara: Translator) {
      const validatedArgs = deleteGlossarySchema.parse(args);
      const { id } = validatedArgs;
      return await lara.glossaries.delete(id);
    }
  • Zod schema for delete_glossary input validation. Requires a string 'id' matching the pattern /^gls_[a-zA-Z0-9_-]+$/ with length 1-255.
    export const deleteGlossarySchema = z.object({
      id: z.string()
        .min(1)
        .max(255)
        .regex(/^gls_[a-zA-Z0-9_-]+$/, "Invalid glossary ID format")
        .describe("The glossary ID to delete (format: gls_*, e.g., 'gls_xyz123')"),
    });
  • src/mcp/tools.ts:48-68 (registration)
    Registration of delete_glossary in the handlers map at line 61, mapping the tool name to the deleteGlossary function.
    const handlers: Record<string, Handler> = {
      detect_language: detectLanguage,
      translate: translateHandler,
      create_memory: createMemory,
      delete_memory: deleteMemory,
      update_memory: updateMemory,
      add_translation: addTranslation,
      delete_translation: deleteTranslation,
      import_tmx: importTmx,
      check_import_status: checkImportStatus,
      get_glossary: getGlossary,
      create_glossary: createGlossary,
      update_glossary: updateGlossary,
      delete_glossary: deleteGlossary,
      import_glossary_csv: importGlossaryCsv,
      check_glossary_import_status: checkGlossaryImportStatus,
      export_glossary: exportGlossary,
      get_glossary_counts: getGlossaryCounts,
      add_glossary_entry: addGlossaryEntry,
      delete_glossary_entry: deleteGlossaryEntry,
    };
  • Tool definition for delete_glossary with name, description, inputSchema, and annotations (destructiveHint: true).
    {
      name: "delete_glossary",
      description:
        "Deletes a glossary from your Lara Translate account.",
      inputSchema: z.toJSONSchema(deleteGlossarySchema),
      annotations: {
        title: "Delete glossary",
        readOnlyHint: false,
        destructiveHint: true,
        openWorldHint: false,
      },
    },
  • Human-readable response formatting for delete_glossary results.
    case "delete_glossary":
      return `Deleted glossary ${result?.id ?? args?.id ?? ""}`;
Behavior3/5

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

Annotations already provide destructiveHint=true and readOnlyHint=false. Description confirms deletion but adds no extra behavioral details (e.g., cascade effects, irreversibility) beyond what annotations convey.

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 is front-loaded with verb and resource, concise with no wasted words.

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?

Description is adequate for a simple one-parameter delete tool but lacks mention of return value, side effects, or restrictions (e.g., glossary with entries). No output schema exists, so some guidance on response would improve completeness.

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?

The input schema covers 100% of parameter documentation with a clear description and pattern. The tool description adds no additional meaning beyond what the schema provides for the 'id' parameter.

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 the action ('Deletes') and the resource ('glossary from your Lara Translate account'), distinguishing it from sibling tools like delete_glossary_entry or delete_memory.

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?

Description implies usage when deletion of a glossary is needed but provides no explicit guidance on when to use this vs. alternatives (e.g., update_glossary) or any prerequisites (e.g., ensure glossary is not in use).

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