Skip to main content
Glama
translated

Lara Translate MCP Server

by translated

check_glossary_import_status

Read-only

Check the current status of a glossary CSV import job by providing the import ID, polling until the import is complete.

Instructions

Checks the status of a glossary CSV import job started by import_glossary_csv. Poll this tool with the import_id returned from import_glossary_csv until the import is complete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the glossary import job

Implementation Reference

  • The main handler function that validates args with the schema, extracts the import job ID, and calls lara.glossaries.getImportStatus(id) to check the status.
    export async function checkGlossaryImportStatus(args: any, lara: Translator) {
      const validatedArgs = checkGlossaryImportStatusSchema.parse(args);
      const { id } = validatedArgs;
    
      return await lara.glossaries.getImportStatus(id);
    }
  • Input validation schema requiring a string 'id' (the glossary import job ID).
    export const checkGlossaryImportStatusSchema = z.object({
      id: z.string().describe("The ID of the glossary import job"),
    });
  • src/mcp/tools.ts:63-63 (registration)
    Registration of the handler in the handlers record mapping tool name 'check_glossary_import_status' to the imported handler function.
    check_glossary_import_status: checkGlossaryImportStatus,
  • Full tool definition including name, description, input schema, annotations (readOnlyHint: true), and invocation metadata.
    {
      name: "check_glossary_import_status",
      description:
        "Checks the status of a glossary CSV import job started by import_glossary_csv. Poll this tool with the import_id returned from import_glossary_csv until the import is complete.",
      inputSchema: z.toJSONSchema(checkGlossaryImportStatusSchema),
      annotations: {
        title: "Check glossary import status",
        readOnlyHint: true,
        destructiveHint: false,
        openWorldHint: false,
      },
      _meta: invocationMeta("Checking glossary import status…", "Status retrieved"),
    },
  • Narration helper that formats the result message for this tool's response.
    case "check_glossary_import_status":
      return `Glossary import status: ${result?.status ?? "unknown"}`;
Behavior5/5

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

The description discloses that this tool is for polling (repeated calls) and is read-only, aligning with annotations (readOnlyHint: true). It adds value beyond annotations by explaining the polling pattern and that the status indicates completion.

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 extremely concise with two sentences. Every sentence adds essential information: what the tool does and how to use it. There is no redundancy or unnecessary detail.

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

Completeness5/5

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

Given the tool's simplicity (1 parameter, polling pattern), the description is complete. It covers purpose, usage, and parameter origin. Annotations handle safety. No output schema is needed for this straightforward polling tool.

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?

The input schema provides full coverage (100%) with a clear description for the 'id' parameter. The description adds context by explaining where the ID comes from (import_glossary_csv), which enhances understanding beyond 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 tool's function: checking the status of a glossary CSV import job. It specifies the resource (glossary import job) and the action (checking status), and distinguishes it from siblings like import_glossary_csv and check_import_status by explicitly mentioning the source of the import ID.

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?

The description explicitly states when to use this tool: poll it with the import_id returned from import_glossary_csv until the import completes. It also implies the prerequisite action (starting an import) and provides a clear usage pattern.

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