Skip to main content
Glama

TMX translation memory export

bpj_tmx_memory_export
Read-onlyIdempotent

Export bilingual segment pairs in a TMX 1.4 translation memory with explicit source and target languages.

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": {
      "from": "<from>",
      "to": "<to>",
      "rows": "<rows>"
    },
    "name": "bpj_tmx_memory_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
fromYes
rowsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds the TMX 1.4 target format and the requirement to state both languages explicitly, but says nothing about whether it writes to disk, returns a string, or how failures surface. Modest added value beyond annotations.

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 filler or redundancy. It earns its place, though it is thin relative to the tool's three required parameters.

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?

For a three-parameter tool with zero schema description coverage and no output schema, the description omits the language-code format, the rows pair syntax expectations, the length limit, and what the export returns or where it goes. An agent could call it, but correctness on inputs is left largely to the schema titles.

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%, so the description should carry the parameter burden and largely does not. It echoes that source and target languages are explicit (mapping to from/to) but gives no language-code convention, and says nothing about the rows parameter's pipe-delimited format or its 3500-character cap beyond what the schema titles already state.

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 (export) and resource (bilingual segment pairs in a TMX 1.4 translation memory), and the format version makes it distinguishable from format-specific siblings like bpj_xliff_unit_export. It does not explicitly name those alternatives, but the resource is concrete enough that an agent knows what it produces.

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 when-to-use or when-not-to-use guidance, and no alternative export tools are referenced. The only implicit routing signal is the TMX format mention, which an agent would have to infer selects this tool over other translation export siblings.

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.