Skip to main content
Glama

XLIFF translation unit export

bpj_xliff_unit_export
Read-onlyIdempotent

Build XLIFF 1.2 trans-units from keys, source strings and translations and reject duplicate IDs.

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>",
      "strings": "<strings>"
    },
    "name": "bpj_xliff_unit_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
fromYes
stringsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds two useful behavioral facts beyond the annotations: the target format version (XLIFF 1.2) and the duplicate-ID rejection failure mode. It still does not say what is returned (an XLIFF document string? a file?) or how the rejection is surfaced to the caller.

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. Slightly terse given the input-format complexity, but nothing is wasted.

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?

No output schema exists, so return semantics had to come from the description, and they are absent — it is unclear whether an XLIFF document is returned or written elsewhere. Combined with unexplained input encoding for a 3-required-parameter tool, the definition is adequate but leaves real gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description only loosely maps its wording onto the three parameters ('keys, source strings and translations' vs. the single 'strings' field plus from/to). It never explains the pipe-delimited 'Key|source|translation' layout or the language-code format, which is the key thing an agent must get right; that detail survives only in the schema titles.

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?

Specific verb and artifact: 'Build XLIFF 1.2 trans-units from keys, source strings and translations', which tells an agent exactly what is produced and from what inputs. It does not differentiate from adjacent export tools (e.g. bpj_tmx_memory_export or the markdown/subtitle exporters), so sibling disambiguation is left to the caller.

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?

No when-to-use guidance, no prerequisites, and no mention of when a different export format (TMX, subtitle, markdown) would be preferable. The only conditional behavior mentioned ('reject duplicate IDs') is about input validation, not tool selection.

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.