Skip to main content
Glama
translated

Lara Translate MCP Server

by translated

check_import_status

Read-only

Monitor a TMX import job's progress by polling its status with the import ID, tracking completion via the progress field.

Instructions

Checks the status of a TMX import job started by import_tmx. Poll this tool with the import_id returned from import_tmx until the import is complete. The response includes a progress field to track completion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the import job

Implementation Reference

  • The handler function that executes the check_import_status tool logic. It validates input with the schema, extracts the 'id' parameter, and calls lara.memories.getImportStatus(id) to check the status of a TMX import job.
    export async function checkImportStatus(args: any, lara: Translator) {
      const validatedArgs = checkImportStatusSchema.parse(args);
      const { id } = validatedArgs;
    
      return await lara.memories.getImportStatus(id);
    }
  • Zod schema defining the input: an object with a single required string field 'id' (the import job ID).
    export const checkImportStatusSchema = z.object({
      id: z.string().describe("The ID of the import job"),
    });
  • src/mcp/tools.ts:57-57 (registration)
    Registration of checkImportStatus in the handlers map under the name 'check_import_status'.
    check_import_status: checkImportStatus,
  • Tool definition entry in toolDefinitions array, including name, description, inputSchema reference, and annotations (readOnlyHint: true).
    {
      name: "check_import_status",
      description:
        "Checks the status of a TMX import job started by import_tmx. Poll this tool with the import_id returned from import_tmx until the import is complete. The response includes a progress field to track completion.",
      inputSchema: z.toJSONSchema(checkImportStatusSchema),
      annotations: {
        title: "Check TMX import status",
        readOnlyHint: true,
        destructiveHint: false,
        openWorldHint: false,
      },
      _meta: invocationMeta("Checking import status…", "Status retrieved"),
    },
  • Narration case in the narrate() function that returns a human-readable status string for check_import_status results.
    case "check_import_status":
      return `TMX import status: ${result?.status ?? "unknown"}`;
Behavior4/5

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

Annotations already provide readOnlyHint=true and destructiveHint=false, so the description adds value by detailing polling behavior and the presence of a progress field. This extra context justifies a slightly higher score.

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?

Three concise sentences with no unnecessary words. The first sentence states purpose, the second gives usage, the third mentions response content. Perfectly front-loaded.

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?

Given no output schema, the description mentions only the progress field. Missing details about final response structure or error conditions. While sufficient for basic use, it could be more complete.

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 schema covers the parameter fully with a description. The description adds value by linking the parameter to import_tmx's return value, providing semantic context beyond the schema.

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 it checks the status of a TMX import job, specifying the companion tool import_tmx and distinguishing it from sibling check_glossary_import_status. The verb 'checks' and resource 'status of a TMX import job' are specific.

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?

Explicitly instructs to poll with the import_id from import_tmx until complete. While it doesn't explicitly exclude other uses, the context and sibling list make the intended usage clear.

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