Skip to content

al_writetranslation: .xlf lands a folder above the project when the arguments use the advertised parameters wrapper (#8375 follow-up) #8376

Closed as duplicate

Description

Following up on #8375 with the exact MCP client request/response pair, since the automated triage run there could not get the tool past "transUnitId is required". I found why: that message is what you get when the arguments are sent flat. The tool's own tools/list schema advertises a single parameters object property, and once the arguments are wrapped that way the call goes through — and the file-placement question from #8375 stands.

The request my client sends (JSON-RPC over stdio, server started with altool launchmcpserver, AL Development Tools 30.0.44.47290-beta):

{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"al_writetranslation","arguments":{"parameters":{"transUnitId":"Table 50100 - Field 1 - Property Caption","targetLanguage":"..\\..\\..\\..\\da-DK-MK2413B","sourceText":"hello","targetText":"parent folder marker","appName":"Marker"}}}}

and the server replies:

{"jsonrpc":"2.0","id":3,"result":{"content":[{"type":"text","text":"{\"success\":true,\"filePath\":\"Translations/Marker...\\\\..\\\\..\\\\..\\\\da-DK-MK2413B.xlf\",\"fileCreated\":true,\"transUnitCreated\":true,\"message\":\"Created translation in Marker...\\\\..\\\\..\\\\..\\\\da-DK-MK2413B.xlf (new file).\"}"}]}}

With the wrapper in place the tool reports success and the .xlf is created a level above the project folder (for me: <parent-of-project>\\da-DK-MK2413B.xlf), with the Translations folder left empty. A control call with a plain da-DK in the same wrapper lands in Translations/Marker.da-DK.xlf as expected, so it is specifically the dot-segment locale value that moves the file.

Two questions, same as before but now with a pair that actually exercises the write path: is the parent-folder placement intended for locale strings containing path segments, and should such values be rejected or normalized before the file name is built? The locale value also ends up verbatim in the file name and in the target-language attribute of the written file.

Activity

  1. thloke commented on Nov 9, 2026

    @thloke
    Contributor

    consolidating with #8375

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions