Skip to main content
Glama
translated

Lara Translate MCP Server

by translated

list_glossaries

Read-only

List all glossaries in your Lara Translate account. Glossaries enforce specific terminology during translation.

Instructions

Lists all glossaries in your Lara Translate account. Glossaries are collections of terms with their translations that enforce specific terminology during translation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual handler function that executes the 'list_glossaries' tool logic. It calls lara.glossaries.list() to retrieve all glossaries.
    export async function listGlossaries(lara: Translator) {
        return await lara.glossaries.list();
    }
  • Input schema for list_glossaries — an empty object, since no parameters are required.
    export const listGlossariesSchema = z.object({});
  • src/mcp/tools.ts:70-74 (registration)
    Registration in the 'listers' record mapping tool name 'list_glossaries' to the listGlossaries handler function.
    const listers: Record<string, Lister> = {
      list_memories: listMemories,
      list_languages: listLanguages,
      list_glossaries: listGlossaries,
    };
  • Tool definition with name, description, inputSchema, and annotations for the MCP tool registration.
    {
      name: "list_glossaries",
      description:
        "Lists all glossaries in your Lara Translate account. Glossaries are collections of terms with their translations that enforce specific terminology during translation.",
      inputSchema: z.toJSONSchema(listGlossariesSchema),
      annotations: {
        title: "List glossaries",
        readOnlyHint: true,
        destructiveHint: false,
        openWorldHint: false,
      },
    },
  • src/mcp/tools.ts:25-25 (registration)
    Import statement for listGlossaries and listGlossariesSchema from the handler file.
    import { listGlossaries, listGlossariesSchema } from "./tools/list_glossaries.js";
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description adds that it lists all glossaries in the account, reinforcing the safe read behavior. No additional behavioral surprises.

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 concise sentences, front-loaded with action, no wasted words. Perfectly structured.

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?

For a tool with no output schema, the description hints at glossary content but does not specify return fields. Adequate but could provide more detail on what properties each glossary object has.

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, so baseline 4 applies. Description does not need to explain parameters but could mention output fields. However, it's acceptable for a parameterless tool.

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?

Clearly states the tool lists all glossaries in the account, with a brief definition of glossaries. Distinguishes from siblings like get_glossary (single) and create_glossary.

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

Usage Guidelines4/5

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

Indicates when to use (to list all glossaries) and implies alternative (get_glossary for a specific one). Missing explicit 'when not to use' but adequate for a simple list tool.

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