Skip to main content
Glama
translated

Lara Translate MCP Server

by translated

delete_memory

Destructive

Remove a specific translation memory from your Lara Translate account using its unique identifier.

Instructions

Deletes a translation memory from your Lara Translate account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe unique identifier of the memory to update. Format: mem_xyz123

Implementation Reference

  • The handler function that executes the delete_memory tool logic. It validates the input using deleteMemorySchema (expects an 'id' string), then calls lara.memories.delete(id) to delete the translation memory.
    export async function deleteMemory(args: any, lara: Translator) {
      const validatedArgs = deleteMemorySchema.parse(args);
      const { id } = validatedArgs;
      return await lara.memories.delete(id);
    }
  • Zod schema for delete_memory input validation. Requires a single 'id' field (string) identifying the memory to delete (format: mem_xyz123).
    export const deleteMemorySchema = z.object({
      id: z
        .string()
        .describe(
          "The unique identifier of the memory to update. Format: mem_xyz123"
        ),
    });
  • src/mcp/tools.ts:52-52 (registration)
    Registration of the deleteMemory handler in the handlers map, mapped to the key 'delete_memory'.
    delete_memory: deleteMemory,
  • Tool definition registration including name, description, inputSchema, and annotations (destructiveHint: true).
    {
      name: "delete_memory",
      description:
        "Deletes a translation memory from your Lara Translate account.",
      inputSchema: z.toJSONSchema(deleteMemorySchema),
      annotations: {
        title: "Delete translation memory",
        readOnlyHint: false,
        destructiveHint: true,
        openWorldHint: false,
      },
    },
  • Narration text for the delete_memory tool result, used for formatting the output content.
    case "delete_memory":
      return `Deleted translation memory ${result?.id ?? args?.id ?? ""}`;
Behavior3/5

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

The description 'Deletes' aligns with annotations' destructiveHint: true, but adds no extra behavioral context (e.g., permissions required, cascading effects, recoverability). With annotations already indicating destructiveness, the description provides minimal additional value.

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?

The description is a single, clear sentence containing all necessary information with no extraneous text. It is optimally concise.

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?

For a simple deletion tool with one parameter, the description is mostly complete. Annotations cover destructive behavior. The only gap is lack of post-deletion outcome details, but given simplicity, this is acceptable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema describes the 'id' parameter as 'the unique identifier of the memory to update', which is misleading for a delete tool. The tool description does not clarify this error or add new semantics. Schema coverage is 100%, so baseline is 3, but the inaccuracy reduces effectiveness.

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 'Deletes' and the resource 'translation memory', and specifies the context 'from your Lara Translate account'. This distinguishes it from sibling tools like create_memory, update_memory, and list_memories.

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?

The description provides no guidance on when to use delete_memory compared to alternatives like update_memory or delete_glossary. It does not mention prerequisites (e.g., the memory must exist) or that the action is irreversible, though annotations hint at destructiveness.

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