@langlink/l10n-mcp 0.4.0 → 0.6.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -1
- package/dist/index.js +1126 -443
- package/dist/index.js.map +4 -4
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -26,11 +26,12 @@ npx -y @langlink/l10n-mcp config --client agents --write
|
|
|
26
26
|
## Tools
|
|
27
27
|
|
|
28
28
|
- `l10n_inspect`, `l10n_match_tm`, `l10n_match_terms`, and `l10n_check` are available over local stdio and Streamable HTTP.
|
|
29
|
+
- For a complete bilingual QA run over local stdio, give the agent a local file and ask it to run full QA and return an HTML report. `l10n_review_start` runs the fixed rules and supplies the V1.1 criteria. The agent submits each batch with `l10n_review_batch`, then calls `l10n_review_report` for a standalone local HTML report with collapsible rule sections and offline Excel export. AIQA uses the host conversation model.
|
|
29
30
|
- `l10n_qa_review` is available over local stdio. It opens the bilingual QA page and returns a loopback URL. A local review process serves the page for up to 30 minutes of inactivity, independently of the stdio conversation. Call the tool again for a new link.
|
|
30
31
|
|
|
31
32
|
The page supports selected-segment AIQA with the Workbench V1.1 decision rules. Set `APERTURE_BASE_URL` and `L10N_AIQA_MODEL` in the connector process and supply `APERTURE_API_KEY` if required by the gateway. Selected segment text, nearby source text and entered project requirements are sent when the user clicks Run AIQA. The per-segment Ask Agent action copies a question with its evidence into the clipboard for use in a host conversation.
|
|
32
33
|
|
|
33
|
-
For WorkBuddy, configure the local connector, complete any trust or enablement prompts in WorkBuddy, then
|
|
34
|
+
For WorkBuddy, configure the local connector, complete any trust or enablement prompts in WorkBuddy, then confirm that the local conversation can call `l10n_review_start`, `l10n_review_batch`, and `l10n_review_report`. [WorkBuddy setup guide](https://github.com/langlink-tech/langlink-harness-toolsets/blob/main/docs/mcp-clients.md#workbuddy)
|
|
34
35
|
|
|
35
36
|
## Environment
|
|
36
37
|
|