Skip to main content
Glama
translated

Lara Translate MCP Server

by translated

list_memories

Read-only

Retrieve all saved translation memories from your Lara Translate account to reuse past translations.

Instructions

Lists all translation memories in your Lara Translate account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the list_memories tool logic. Calls lara.memories.list() to fetch all translation memories.
    export async function listMemories(lara: Translator) {
        return await lara.memories.list()
    }
  • Input schema definition for list_memories — an empty object (no parameters required).
    export const listMemoriesSchema = z.object({})
  • Tool definition registration for list_memories in the toolDefinitions array, including description, inputSchema, and annotations (readOnlyHint, destructiveHint).
    {
      name: "list_memories",
      description:
        "Lists all translation memories in your Lara Translate account.",
      inputSchema: z.toJSONSchema(listMemoriesSchema),
  • src/mcp/tools.ts:71-71 (registration)
    Registration of listMemories in the listers record, mapping the tool name to the handler for zero-argument tool calls.
    list_memories: listMemories,
  • src/mcp/tools.ts:24-24 (registration)
    Import of listMemories and listMemoriesSchema from the implementation file.
    import { listMemories, listMemoriesSchema } from "./tools/list_memories.js";
Behavior3/5

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

Annotations already declare readOnlyHint and destructiveHint. The description adds minimal context beyond 'in your account'. No disclosure of pagination or sorting behavior.

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, front-loaded with key information. No unnecessary 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?

No output schema, but description does not mention return format, pagination, or ordering. However, for a simple list tool with no parameters, it is minimally 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?

No parameters exist (0 parameters), and schema coverage is 100%. Per guidelines, baseline is 4. Description adds no parameter info but is not necessary.

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 uses specific verb 'lists' and resource 'translation memories', clearly distinguishing from siblings like create_memory or delete_memory. The scope 'in your Lara Translate account' is precise.

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?

No explicit guidance on when to use this tool versus alternatives such as list_glossaries. Context is implied but not clarified.

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