Skip to main content
Glama

Translation memory conflicts

bpj_translation_conflict_review
Read-onlyIdempotent

Identify source segments mapped to multiple distinct translations in a bilingual list.

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": {
      "rows": "<rows>"
    },
    "name": "bpj_translation_conflict_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds no further behavioral context: it does not say how conflicts are detected (exact match vs. normalization, case sensitivity, whitespace trimming), what happens when no conflict exists, or what form the result takes. With annotations carrying the safety burden, this is acceptable but thin.

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?

A single front-loaded sentence with no filler, hedges, or redundant restatement of the tool name. Every word earns its place.

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?

With no output schema, the description would ideally say what the conflict report contains (e.g., which sources conflict and how many variants each has). It also omits whether output is empty when no conflicts are found. The tool itself is simple and single-parameter, so this is a moderate gap rather than a critical one.

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?

There is one required parameter with 0% description coverage, so the description is supposed to compensate; it only says 'bilingual list' and never explains the pipe-delimited 'Source|translation' row format or the 3500-character limit. Those details do exist in the schema's title field, which keeps this from being a genuine gap, but the description itself contributes almost no parameter meaning.

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 uses a specific verb ('Identify') with a precisely defined object ('source segments mapped to multiple distinct translations in a bilingual list'). It is clear what the tool does, but it offers no differentiation from the many other bpj_* review tools in the sibling list, so an agent must read the name to know this one is about translation-memory conflicts rather than HTML, subtitles, or English prose reviews.

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?

The phrase 'in a bilingual list' hints at the input context but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent is left to infer that this tool applies only after source and translation pairs already exist and before a TM is finalized.

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.