Skip to main content
Glama

tm_import

Import a TMX/XLIFF file’s text into translation memory (free; async embeddings).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "format": "<format>",
      "content": "<content>"
    },
    "name": "tm_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatYes
contentYes
project_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose two meaningful traits beyond the schema: the operation is free and embeddings are generated asynchronously, which implies the call may return before the data is fully searchable. It does not say what happens to duplicate or existing entries, whether permissions are required, or how to track the async work (e.g., via processing_job_get).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no wasted wording; the parenthetical efficiently packs cost and async behavior. It is arguably too terse for a 3-parameter, no-annotation mutation tool, but nothing is redundant.

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

Completeness2/5

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

With no annotations, no output schema, and 0% parameter coverage, the description leaves substantial gaps: the role of project_id, expected response shape, duplicate-handling behavior, and how to poll the async embedding job are all unstated. For a write-oriented import tool this is inadequate context.

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?

Schema description coverage is 0% across three parameters. The description only indirectly clarifies that 'format' is a TMX/XLIFF choice and that 'content' is the file text; 'project_id' is never mentioned, so an agent has no idea whether it is required for scoping or what happens when omitted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb (import) and resource (TMX/XLIFF text into translation memory), which lets an agent distinguish it from siblings like tm_query or strings_import. It stops short of explicitly naming which sibling handles the alternative case, but the action is unambiguous.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named. The parenthetical '(free; async embeddings)' hints that cost and latency are considerations, but the agent must infer that this tool is for bulk-loading existing translation files rather than, say, querying or importing strings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources