Skip to main content
Glama
translated

Lara Translate MCP Server

by translated

delete_glossary_entry

Destructive

Delete a glossary entry from your Lara Translate account by specifying the glossary ID and either a term (monodirectional) or GUID (multidirectional).

Instructions

Deletes an entry from a glossary in your Lara Translate account. Use term for monodirectional glossaries or guid for multidirectional glossaries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe glossary ID (format: gls_*, e.g., 'gls_xyz123')
termNoThe term to delete. Use this for monodirectional glossaries.
guidNoThe entry GUID to delete. Use this for multidirectional glossaries.

Implementation Reference

  • The main handler function that parses args (id, term, guid) using Zod schema and calls lara.glossaries.deleteEntry().
    export async function deleteGlossaryEntry(args: unknown, lara: Translator) {
      const { id, term, guid } = deleteGlossaryEntrySchema.parse(args);
    
      if (!term && !guid) {
        throw new InvalidInputError("At least one of 'term' or 'guid' must be provided");
      }
    
      return await lara.glossaries.deleteEntry(id, term, guid);
    }
  • Zod schema defining input validation: id (required, gls_* format), term (optional object with language and value), guid (optional string).
    export const deleteGlossaryEntrySchema = 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')"),
      term: z.object({
        language: z.string().describe("The language code of the term"),
        value: z.string().describe("The term value"),
      }).optional().describe("The term to delete. Use this for monodirectional glossaries."),
      guid: z.string().optional().describe(
        "The entry GUID to delete. Use this for multidirectional glossaries."
      ),
    });
  • src/mcp/tools.ts:67-67 (registration)
    Registration of the handler function in the handlers record under the key 'delete_glossary_entry'.
    delete_glossary_entry: deleteGlossaryEntry,
  • Tool metadata (name, description, inputSchema, annotations) registered in the tool list for MCP discovery.
    {
      name: "delete_glossary_entry",
      description:
        "Deletes an entry from a glossary in your Lara Translate account. Use term for monodirectional glossaries or guid for multidirectional glossaries.",
      inputSchema: z.toJSONSchema(deleteGlossaryEntrySchema),
  • Case in the result description switch statement for the 'delete_glossary_entry' action.
    case "delete_glossary_entry":
      return "Deleted entry from glossary";
Behavior4/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds value by specifying the two deletion strategies, which is behavioral context beyond what annotations provide. No contradiction.

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: first states the purpose, second provides actionable guidance. No filler, front-loaded, every word earns its place.

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

Completeness4/5

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

The description covers core behavior and parameter usage. Lacks explicit mention of return values (no output schema), but for a delete operation this is often implicit. With annotations present, completeness is adequate.

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?

Schema descriptions are detailed (100% coverage), but the description adds crucial context about when to use 'term' vs 'guid', which is not inferable from the schema alone.

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 action (deletes an entry) and the specific resource (glossary in Lara Translate account). It distinguishes usage for monodirectional vs. multidirectional glossaries, effectively differentiating the tool from siblings like delete_glossary or delete_translation.

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

Usage Guidelines5/5

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

Provides explicit guidance on when to use 'term' (monodirectional glossaries) versus 'guid' (multidirectional glossaries). This helps the agent select the correct parameter, and the sibling list confirms no overlapping functionality.

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