@tencentcloud/sdk-mcp 1.7.4 → 1.7.6

package/tools/definitions/finalize_answer_def.js

@@ -1,27 +1,28 @@
 export const FOLLOWUP_QUESTION = '以上是否解决了您的问题？请回复「已解决」或「未解决」，方便我们进一步优化回答质量。';
 const TOOL_DESCRIPTION = `
 Purpose:
-Finalize a search_trtc_knowledge answer and return the follow-up text to append.
+Finalize the answer in current consultation and return the follow-up text.
 
-When to call:
-- After all searches/fetches are done and the final answer is drafted, MUST call this tool exactly once before replying to the user.
-- Do NOT call it for intermediate searches, partial drafts, or when another search/fetch is still needed.
+When to call (hard rule):
+- Call exactly once after all searches are done and final answer is ready.
+- MUST be called before replying final answer to user.
+- Do NOT call for drafts, intermediate reasoning, or unfinished retrieval.
 
-Input:
-- prompt: Original user question. Must match the search_trtc_knowledge prompt.
-- answer: Full synthesized answer (same text sent to the user).
-- queryID: REQUIRED. Must match the non-empty queryID returned by search_trtc_knowledge.
-- product/framework: Reuse the same values from the search_trtc_knowledge chain when available.
+Input contract:
+- prompt: original user question, consistent with search_trtc_knowledge prompt.
+- answer: final user-facing answer text.
+- queryID: REQUIRED, non-empty queryID from search_trtc_knowledge.
+- product/framework: reuse values from the same consultation chain when available.
 
-Returns:
-- Follow-up text. Append it as-is after the answer.
-- Do NOT write your own follow-up question.
+Output contract:
+- Return follow-up text and append it as-is after answer.
+- Do NOT write custom follow-up wording.
 `;
 const PARAMETER_DESCRIPTIONS = {
-    prompt: 'Original user question. Must match search_trtc_knowledge.',
-    answer: 'Full synthesized answer (same text sent to the user).',
-    product: 'Reuse product from the search_trtc_knowledge chain when available.',
-    framework: 'Reuse framework from the search_trtc_knowledge chain when available.',
+    prompt: 'Original user question. Must match search_trtc_knowledge prompt.',
+    answer: 'Final synthesized answer, same content sent to user.',
+    product: 'Reuse product from current search_trtc_knowledge chain when available.',
+    framework: 'Reuse framework from current search_trtc_knowledge chain when available.',
     queryID: 'REQUIRED. Non-empty queryID returned by search_trtc_knowledge.',
 };
 export const FINALIZE_ANSWER_DEFINITION = {

package/tools/definitions/get_native_call_uikit_integration_def.js

@@ -1,32 +1,41 @@
 import { INTEGRATION_BOUNDARY_SUFFIX } from './integration-boundary.js';
 const TOOL_DESCRIPTION = `
-用途：
-返回 Native TUICallKit preset 集成文档，供 AI 完成移动端音视频通话接入与代码生成（预制通话界面、开箱即用）。
+Purpose:
+Return Native TUICallKit preset integration docs for explicit codegen implementation.
 
-典型适用问题（共用触发词，可能同时命中 'get_native_callkit_core_integration' Core 工具）：
+When to call (MUST):
+- User explicitly asks for runnable project integration code or concrete implementation steps.
+
+When NOT to call:
+- Pure feature Q&A, documentation lookup, API/component explanation, troubleshooting.
+
+Scope details:
+Returns Native TUICallKit preset integration documentation for implementing mobile audio/video calling with ready-made UI.
+
+Common trigger lexicon (may overlap with 'get_native_callkit_core_integration' Core 工具）：
 集成 CallKit, 接入 CallKit, 音视频通话, 语音通话, 视频通话, 1v1 通话, 多人通话, 通话功能, 拨打电话, 接听电话, 来电, 离线推送, VoIP
-命中以上共用触发词时，请**先主动追问用户**："您希望使用默认通话界面快速集成（TUICallKit preset），还是基于 Core SDK 自定义通话界面？" 用户选择"默认/preset"后再调用本工具；选择"自定义/Core"则调用 'get_native_callkit_core_integration'。
+When only common triggers are hit, ask a clarification first: "Do you prefer preset default UI (TUICallKit) or Core SDK custom UI?" Call this tool only after user chooses preset/default; if user chooses custom/Core, call 'get_native_callkit_core_integration'.
 
-典型适用问题（preset 专属触发词，仅命中本工具，无需追问，直接调用）：
+Preset-only trigger lexicon (direct call, no clarification needed):
 TUICallKit, Native TUICallKit, Native Call UIKit, preset, preset 集成, 预制 UI, 预制通话界面, 默认 UI, 默认通话界面, 开箱即用通话界面, 现成的通话页面, 通话界面已经有了, TUICallKit Flutter, TUICallKit Android, TUICallKit iOS
 
-输入：
+Inputs:
 - framework: flutter | android | ios
-- prompt: 用户的原始问题全文，保留完整上下文，不要压缩成关键词摘要
+- prompt: Original user question. Keep full context; do not compress into keyword summary.
 
-返回：
-- content: [{ type: 'text', text: 文档正文或说明文本 }]
+Outputs:
+- content: [{ type: 'text', text: Documentation body or explanatory text }]
 
-边界：
-- 当用户未明确平台或框架时，应先调用 'present_framework_choice'
-- framework=uni-app 时不支持本工具（preset 无 uni-app 端），请改用 'get_native_callkit_core_integration'
-- 当用户已明示「自定义 UI」「Core SDK」「AtomicXCore」「CallStore」「自己画通话页面」等 Core 专属触发词时，直接调用 'get_native_callkit_core_integration'，不要走本工具
-- 面向 Native CallKit preset 整体集成，不负责平台选择，也不负责铃声、虚拟背景、头像昵称、悬浮窗等单功能/API 设置问题
+Boundaries:
+- If platform/framework is not specified, call 'present_framework_choice' first.
+- framework=uni-app is not supported by this preset tool (no preset uni-app support). Use 'get_native_callkit_core_integration' instead.
+- If user explicitly indicates Core intent (e.g. custom UI / Core SDK / AtomicXCore / CallStore / self-built call page), call 'get_native_callkit_core_integration' directly.
+- This tool targets end-to-end Native CallKit preset integration. It does not handle platform selection or isolated single-feature/API setup topics (e.g. ringtone, virtual background, avatar/nickname, floating window).
 ${INTEGRATION_BOUNDARY_SUFFIX}
 `;
 const PARAMETER_DESCRIPTIONS = {
-    framework: '目标平台。参数名固定为 framework，禁止传 platform。可选值：flutter | android | ios。',
-    prompt: '用户的原始问题全文，保留完整上下文，不要压缩成关键词摘要。',
+    framework: 'Target platform. Parameter name must be framework (not platform). Allowed values: flutter | android | ios。',
+    prompt: 'Original user question. Keep full context; do not compress into keyword summary.',
 };
 export const GET_NATIVE_CALL_UIKIT_INTEGRATION_DEFINITION = {
     name: 'get_native_call_uikit_integration',

package/tools/definitions/get_native_callkit_core_integration_def.js

@@ -1,56 +1,67 @@
 import { INTEGRATION_BOUNDARY_SUFFIX } from './integration-boundary.js';
 const TOOL_DESCRIPTION = `
-用途：
-返回基于 AtomicXCore SDK 的 Native CallKit Core 基础集成文档，适合需要自定义通话界面（无预制 UI）的开发者完成拨打、接听和离线推送的接入。
+Purpose:
+Return Native CallKit Core integration docs for explicit codegen implementation.
 
-典型适用问题（共用触发词，可能同时命中 'get_native_call_uikit_integration' preset 工具）：
+When to call (MUST):
+- User explicitly asks for runnable project integration code or concrete implementation steps.
+
+When NOT to call:
+- Pure feature Q&A, documentation lookup, API/component explanation, troubleshooting.
+
+Scope details:
+Returns Native CallKit Core integration documentation based on AtomicXCore SDK, for custom calling UI (no preset UI) including call, answer, and offline push flows.
+
+Common trigger lexicon (may overlap with 'get_native_call_uikit_integration' preset 工具）：
 集成 CallKit, 接入 CallKit, 音视频通话, 语音通话, 视频通话, 1v1 通话, 多人通话, 通话功能, 拨打电话, 接听电话, 来电, 离线推送, VoIP
-命中以上共用触发词时，请**先主动追问用户**："您希望使用默认通话界面快速集成（TUICallKit preset），还是基于 Core SDK 自定义通话界面？" 用户选择"自定义/Core"后再调用本工具；选择"默认/preset"则调用 'get_native_call_uikit_integration'。
+When only common triggers are hit, ask a clarification first: "Do you prefer preset default UI (TUICallKit) or Core SDK custom UI?" Call this tool only after user chooses custom/Core; if user chooses preset/default, call 'get_native_call_uikit_integration'.
 
-典型适用问题（Core SDK 专属触发词，仅命中本工具，无需追问，直接调用）：
+Core-SDK-only trigger lexicon (direct call, no clarification needed):
 Core SDK, AtomicXCore, 无 UI, 自定义 UI, 自定义通话界面, 自己画通话页面, 不用默认 UI, 修改通话样式, CallStore, CallCoreView, DeviceStore
 
-输入：
+Inputs:
 - framework: android | ios | flutter | uni-app
-- goals: 功能模块列表（make_call | answer_call | offline_push）
-- prompt: 用户的原始问题全文，保留完整上下文，不要压缩成关键词摘要
+- goals: Feature module list (make_call | answer_call | offline_push)
+- prompt: Original user question. Keep full context; do not compress into keyword summary.
 
-返回：
-- content: [{ type: 'text', text: 文档正文或说明文本 }]
+Outputs:
+- content: [{ type: 'text', text: Documentation body or explanatory text }]
 
-边界：
-- 当用户未明确平台或框架时，应先调用 'present_framework_choice'
-- framework=uni-app 时仅支持本工具（Core SDK），不存在 TUICallKit preset 路径；用户选 uni-app 后**不要**再追问"默认 UI vs 自定义 UI"，直接调用本工具
-- framework=uni-app 且 goals 包含 offline_push 时，本工具会返回降级说明文本（uni-app Core 暂无离线推送集成文档），请引导用户参考 Android / iOS offline-push 文档结合 uni-app 原生插件机制自行接入 FCM / APNs，或改用 TUICallKit preset 方案
-- 面向 Core / Store 级基础集成主路径（CallStore 拨打与接听 + 离线推送），不负责美颜、虚拟背景、悬浮窗、画中画等单功能 API 设置
-- 返回的是 Core SDK 基础集成文档，不是完整的预制 UIKit 页面模板
+Boundaries:
+- If platform/framework is not specified, call 'present_framework_choice' first.
+- For framework=uni-app, only this Core tool is supported (no TUICallKit preset path). Do not ask preset vs custom UI again; call this tool directly.
+- If framework=uni-app and goals include offline_push, this tool returns a fallback note (no official uni-app Core offline-push doc yet). Guide user to Android/iOS offline-push docs with native plugin bridging for FCM/APNs, or switch to TUICallKit preset.
+- Focuses on Core/Store-level primary integration path (CallStore call + answer + offline push), not single-feature API tuning such as beauty, virtual background, floating window, or picture-in-picture.
+- Returns Core SDK baseline integration docs, not a complete preset UIKit page template.
 ${INTEGRATION_BOUNDARY_SUFFIX}
 `;
 const PARAMETER_DESCRIPTIONS = {
-    framework: '目标平台。参数名固定为 framework，禁止传 platform。可选值：android | ios | flutter | uni-app。注意：uni-app 仅支持本工具（Core SDK），不存在 TUICallKit preset 路径；用户选 uni-app 时不需要追问"默认 UI vs 自定义 UI"。',
-    goals: '功能列表。可选值：make_call（拨打电话）| answer_call（接听电话）| offline_push（离线推送）。允许多选，例如同时需要拨打和接听时传 ["make_call", "answer_call"]。注意：framework=uni-app 且 goals 包含 offline_push 时，本工具会返回降级说明而非完整文档（uni-app Core 暂无离线推送集成示例）。',
-    prompt: '用户的原始问题全文，保留完整上下文，不要压缩成关键词摘要。',
+    framework: 'Target platform. Parameter name must be framework (not platform). Allowed values: android | ios | flutter | uni-app. Note: uni-app supports only this Core tool (no TUICallKit preset path), and no extra preset-vs-custom question is needed.',
+    goals: 'Goals list. Allowed values: make_call | answer_call | offline_push. Multi-select is allowed (e.g. ["make_call", "answer_call"]). Note: if framework=uni-app and goals include offline_push, this tool returns fallback guidance instead of full docs (no official uni-app Core offline-push example yet).',
+    prompt: 'Original user question. Keep full context; do not compress into keyword summary.',
 };
-const ANTI_HALLUCINATION_HEADER = `本文档基于 AtomicXCore SDK，严禁使用 TUILogin、TUICallKit 等含 UI 的 API。\n\n`;
+const ANTI_HALLUCINATION_HEADER = `This document is based on AtomicXCore SDK. DO NOT use UI-layer APIs such as TUILogin or TUICallKit.\n\n`;
 const ANTI_HALLUCINATION_CONSTRAINT = `
 ---
-【AI 代码生成约束 - AtomicXCore 方案】
-本文档使用 AtomicXCore SDK（无 UI 集成方案）。请严格基于文档内容生成代码，禁止引入文档未提及的 API。
+[AI Code Generation Constraints - AtomicXCore]
+This document describes an AtomicXCore (no-UI) integration path.
+Generate code strictly from documented APIs only, and do NOT introduce undocumented classes or methods.
 
-原则：如果某个 API 或类名在本文档中从未出现，则不要在生成的代码中使用它。
+Rule:
+If an API/class name does not appear in this document, do NOT use it in generated code.
 `;
 const UNI_APP_OFFLINE_PUSH_FALLBACK = `
 # uni-app Core SDK 暂未提供离线推送集成示例
 
-## 现状
+## Current status
 当前 AtomicXCore for uni-app 尚未发布配套的离线推送（FCM / APNs）集成文档与示例代码。
 
-## 推荐做法
+## Recommended approach
 - 参考 Android 平台 \`callkit/core-sdk/android/offline-push.md\`，结合 uni-app 的原生 Android 插件机制接入 FCM Data Message。
 - 参考 iOS 平台 \`callkit/core-sdk/ios/offline-push.md\`，结合 uni-app 的原生 iOS 插件机制接入 VoIP Push。
 - 若不希望自行实现原生插件，建议改用 \`get_native_call_uikit_integration\` 工具集成 TUICallKit preset 方案，该方案 uni-app 端已内置离线推送能力。
 
-## 不要做的事
+## Do NOT
 - 不要凭空生成 uni-app Core 的离线推送代码，可能与官方 SDK 行为不一致。
 - 不要把 Android / iOS 的离线推送代码原样塞进 uni-app 项目，需要走原生插件桥接。
 `;

package/tools/definitions/get_native_chat_uikit_integration_def.js

@@ -1,28 +1,37 @@
 import { INTEGRATION_BOUNDARY_SUFFIX } from './integration-boundary.js';
 const TOOL_DESCRIPTION = `
-用途：
-返回 Native Chat UIKit 集成文档，供 AI 完成移动端 IM 应用接入或聊天窗口接入。
+Purpose:
+Return Native Chat UIKit integration docs for explicit codegen implementation.
 
-典型适用问题：
+When to call (MUST):
+- User explicitly asks for runnable project integration code or concrete implementation steps.
+
+When NOT to call:
+- Pure feature Q&A, documentation lookup, API/component explanation, troubleshooting.
+
+Scope details:
+Returns Native Chat UIKit integration documentation for mobile IM app integration or chat-window embedding.
+
+Common trigger lexicon:
 Native Chat UIKit, TUIKit, IM, 聊天, 会话列表, 聊天窗口, Flutter, Android, iOS, full-featured, chat-only, 客服, 问诊
 
-输入：
+Inputs:
 - framework: flutter | android | ios
 - goals: [full-featured] | [chat-only]
-- prompt: 用户的原始问题全文，保留完整上下文，不要压缩成关键词摘要
+- prompt: Original user question. Keep full context; do not compress into keyword summary.
 
-返回：
-- content: [{ type: 'text', text: 文档正文或说明文本 }]
+Outputs:
+- content: [{ type: 'text', text: Documentation body or explanatory text }]
 
-边界：
-- 当用户未明确平台或框架时，应先调用 'present_framework_choice'
-- 面向 Native Chat UIKit 整体集成，不负责平台选择或单功能深挖
+Boundaries:
+- If platform/framework is not specified, call 'present_framework_choice' first.
+- Targets end-to-end Native Chat UIKit integration, not platform selection or deep single-feature exploration.
 ${INTEGRATION_BOUNDARY_SUFFIX}
 `;
 const PARAMETER_DESCRIPTIONS = {
-    framework: '目标平台。参数名固定为 framework，禁止传 platform。可选值：flutter | android | ios。android/ios 为 codegen 主路径（Compose / SwiftUI）；View/UIKit 集成查阅请用 search_trtc_knowledge。',
-    goals: '功能目标数组。仅允许传一个值，可选值：full-featured（完整应用）| chat-only（单聊天窗口）。',
-    prompt: '用户的原始问题全文，保留完整上下文，不要压缩成关键词摘要。',
+    framework: 'Target platform. Parameter name must be framework (not platform). Allowed values: flutter | android | ios. Android/iOS are primary codegen paths (Compose/SwiftUI). For View/UIKit integration reference, use search_trtc_knowledge.',
+    goals: 'Goal list. Exactly one value is allowed: full-featured | chat-only.',
+    prompt: 'Original user question. Keep full context; do not compress into keyword summary.',
 };
 export const GET_NATIVE_CHAT_UIKIT_INTEGRATION_DEFINITION = {
     name: 'get_native_chat_uikit_integration',

package/tools/definitions/get_native_live_uikit_integration_def.js

@@ -1,35 +1,44 @@
 import { INTEGRATION_BOUNDARY_SUFFIX } from './integration-boundary.js';
 const TOOL_DESCRIPTION = `
-用途：
-返回基于 TUILiveKit 预制 UI 组件的 Native 视频直播集成文档，供 AI 完成移动端（Android / iOS）视频直播的开箱即用界面接入与代码生成。覆盖直播列表页（观众入口）、主播开播页、观众观看页，均为含完整交互 UI 与业务逻辑的预制组件（如 AnchorPrepareView、直播列表瀑布流视图等）。
+Purpose:
+Return Native TUILiveKit preset integration docs for explicit codegen implementation.
 
-典型适用问题（共用触发词，可能同时命中 'get_native_livekit_core_integration' Core 工具）：
+When to call (MUST):
+- User explicitly asks for runnable project integration code or concrete implementation steps.
+
+When NOT to call:
+- Pure feature Q&A, documentation lookup, API/component explanation, troubleshooting.
+
+Scope details:
+Returns Native video-live integration documentation based on TUILiveKit preset UI components, for mobile (Android/iOS) runnable code generation and integration. Coverage includes live list (audience entry), host streaming page, and audience viewing page with complete preset UI interactions and business flow.
+
+Common trigger lexicon (may overlap with 'get_native_livekit_core_integration' Core tool):
 集成 LiveKit, 接入 TUILiveKit, 视频直播, 直播开播, 主播开播, 观众观看, 直播列表, 开播页, 观看页, 直播间列表, Android, iOS
-命中以上共用触发词时，请**先主动追问用户**："您希望使用默认直播界面快速集成（TUILiveKit preset），还是基于 Core SDK / AtomicXCore 自定义直播界面？" 用户选择"默认/preset"后再调用本工具；选择"自定义/Core"则调用 'get_native_livekit_core_integration'。
+When only common triggers are hit, ask a clarification first: "Do you prefer preset default live UI (TUILiveKit) or custom live UI based on Core SDK/AtomicXCore?" Call this tool only after user chooses preset/default; if user chooses custom/Core, call 'get_native_livekit_core_integration'.
 
-典型适用问题（preset 专属触发词，仅命中本工具，无需追问，直接调用）：
+Preset-only trigger lexicon (direct call, no clarification needed):
 TUILiveKit, Native TUILiveKit, Native Live UIKit, preset, preset 集成, 预制 UI, 预制开播页, 预制观看页, 预制直播列表, 默认直播界面, 开箱即用直播界面, 现成的开播页面, 直播界面已经有了, TUILiveKit Android, TUILiveKit iOS, AnchorPrepareView
 
-输入：
+Inputs:
 - framework: android | ios
-- goals: 功能模块列表（可多选，返回时按 直播列表→开播→观看 顺序组织）
-- prompt: 用户的原始问题全文，保留完整上下文，不要压缩成关键词摘要
-
-返回：
-- content: [{ type: 'text', text: 文档正文（含各平台通用的环境准备/依赖接入 + 所选功能页的集成步骤与代码）}]
-
-边界：
-- 仅面向**视频直播（live）**场景。语聊房（voice / 语聊 / 音频房 / 麦位）**不在本工具范围**，如遇该需求请改用 'get_native_livekit_core_integration' 或告知用户暂不支持预制 UI
-- framework 仅支持 android | ios（TUILiveKit 视频直播预制 UI 暂无 flutter / uni-app 端文档，如遇该需求请改用 'get_native_livekit_core_integration' 或告知用户暂不支持）
-- 当用户未明确平台时，应先调用 'present_framework_choice'
-- 当用户已明示「自定义 UI」「Core SDK」「AtomicXCore」「LiveCoreView」「自己画直播页面」等 Core 专属触发词时，直接调用 'get_native_livekit_core_integration'，不要走本工具
-- 面向主播开播 / 观众观看 / 直播列表整体页面集成，不负责连麦、PK、礼物、弹幕、美颜、音效等单功能扩展（这些请使用 'search_trtc_knowledge'）
+- goals: Feature module list (multi-select allowed; output is organized in order: live list -> host streaming -> audience viewing).
+- prompt: Original user question. Keep full context; do not compress into keyword summary.
+
+Outputs:
+- content: [{ type: 'text', text: Documentation body (including platform-common setup/dependency steps plus integration steps and code for selected pages) }]
+
+Boundaries:
+- This tool is only for **video live (live)** scenario. Voice-room needs are out of scope; use 'get_native_livekit_core_integration' instead.
+- framework supports android | ios only. There is no preset TUILiveKit doc for flutter/uni-app; for those needs, use 'get_native_livekit_core_integration'.
+- If platform is missing, call 'present_framework_choice' first.
+- If user explicitly indicates Core intent (e.g. custom UI / Core SDK / AtomicXCore / LiveCoreView / self-built live page), call 'get_native_livekit_core_integration' directly.
+- Targets end-to-end pages (host streaming / audience viewing / live list), not single-feature extensions such as co-host, PK, gifts, danmaku, beauty, or audio effects (use 'search_trtc_knowledge' for those).
 ${INTEGRATION_BOUNDARY_SUFFIX}
 `;
 const PARAMETER_DESCRIPTIONS = {
-    framework: '目标平台。参数名固定为 framework，禁止传 platform。可选值：android | ios。',
-    goals: '功能列表（可多选）。可选值：live_list（直播列表页，观众入口）| host_streaming（主播开播页）| audience_streaming（观众观看页）。做完整移动端直播 App 通常需要 live_list + host_streaming + audience_streaming。',
-    prompt: '用户的原始问题全文，保留完整上下文，不要压缩成关键词摘要。',
+    framework: 'Target platform. Parameter name must be framework (not platform). Allowed values: android | ios.',
+    goals: 'Goal list (multi-select). Allowed values: live_list | host_streaming | audience_streaming. A complete mobile live app usually includes all three goals.',
+    prompt: 'Original user question. Keep full context; do not compress into keyword summary.',
 };
 export const GET_NATIVE_LIVE_UIKIT_INTEGRATION_DEFINITION = {
     name: 'get_native_live_uikit_integration',

package/tools/definitions/get_native_livekit_core_integration_def.js

@@ -1,31 +1,40 @@
 import { INTEGRATION_BOUNDARY_SUFFIX } from './integration-boundary.js';
 const TOOL_DESCRIPTION = `
-用途：
-返回基于 AtomicXCore SDK 的 Native LiveKit Core 基础集成文档，适合实现视频直播或语聊房的开播、观看和房间列表。视频直播场景重点覆盖主播开播、观众观看、直播列表；语聊房场景重点覆盖房主开房、听众进房、语聊房列表。
+Purpose:
+Return Native LiveKit Core integration docs for explicit codegen implementation.
 
-典型适用问题：
+When to call (MUST):
+- User explicitly asks for runnable project integration code or concrete implementation steps.
+
+When NOT to call:
+- Pure feature Q&A, documentation lookup, API/component explanation, troubleshooting.
+
+Scope details:
+Returns Native LiveKit Core integration documentation based on AtomicXCore SDK, for implementing host start, audience viewing, and room list in video live or voice-room scenarios.
+
+Common trigger lexicon:
 Native LiveKit Core, AtomicXCore, 无 UI SDK, Core SDK, 视频直播, 语聊房, 开播, 观看, 房间列表, Android, iOS, Flutter, uni-app, live, voice
 
-输入：
+Inputs:
 - scenario: live | voice
 - framework: android | ios | flutter | uni-app
-- goals: 功能模块列表
-- prompt: 用户的原始问题全文，保留完整上下文，不要压缩成关键词摘要
+- goals: Feature module list
+- prompt: Original user question. Keep full context; do not compress into keyword summary.
 
-返回：
-- content: [{ type: 'text', text: 文档正文或说明文本 }]
+Outputs:
+- content: [{ type: 'text', text: Documentation body or explanatory text }]
 
-边界：
-- 当用户未明确平台或框架时，应先调用 'present_framework_choice'
-- 面向基于 AtomicXCore SDK 的视频直播或语聊房基础集成主路径，不负责连麦、PK、成员列表、美颜、音效、弹幕、礼物等功能扩展
-- 返回的是 Core/Store 级基础集成文档，不是完整预制 UIKit 页面模板
+Boundaries:
+- If platform/framework is not specified, call 'present_framework_choice' first.
+- Targets baseline integration path for video live or voice room on AtomicXCore SDK, not feature extensions such as co-host, PK, member list, beauty, audio effects, danmaku, or gifts.
+- Returns Core/Store-level baseline integration docs, not complete preset UIKit page templates.
 ${INTEGRATION_BOUNDARY_SUFFIX}
 `;
 const PARAMETER_DESCRIPTIONS = {
-    scenario: '场景类型。可选值：live（视频直播）| voice（语聊房）。当需求是开播、观看、房间列表时使用 integration；当需求是连麦、PK、成员列表、美颜、音效、弹幕、礼物时请改用 search_trtc_knowledge 检索。',
-    framework: '目标平台。参数名固定为 framework，禁止传 platform。可选值：android | ios | flutter | uni-app。',
-    goals: '功能列表。可选值：host_streaming（主播/房主开播）| audience_streaming（观众/听众观看）| live_list（房间列表）。',
-    prompt: '用户的原始问题全文，保留完整上下文，不要压缩成关键词摘要。',
+    scenario: 'Scenario type. Allowed values: live | voice. Use this integration tool for host start / audience viewing / room list; for feature extensions (co-host, PK, member list, beauty, audio effects, danmaku, gifts), use search_trtc_knowledge.',
+    framework: 'Target platform. Parameter name must be framework (not platform). Allowed values: android | ios | flutter | uni-app.',
+    goals: 'Goals list. Allowed values: host_streaming | audience_streaming | live_list.',
+    prompt: 'Original user question. Keep full context; do not compress into keyword summary.',
 };
 export const GET_NATIVE_LIVEKIT_CORE_INTEGRATION_DEFINITION = {
     name: 'get_native_livekit_core_integration',

package/tools/definitions/get_usersig_def.js

@@ -1,26 +1,33 @@
 const TOOL_DESCRIPTION = `
-用途：
-使用 MCP 环境变量中的 SDKAppID 和 secretKey 生成测试用 userSig，供 IM 或 TRTC 本地联调使用。
+Purpose:
+Generate a test userSig using SDKAppID and secretKey from MCP environment variables, for IM/TRTC local debugging.
 
-典型适用问题：
-为指定 userID 生成 userSig, 生成测试凭证, 本地联调凭证, userID 对应的 userSig, SDKAppID, secretKey, IM, TRTC, 登录凭证
+When to call (MUST):
+- User explicitly asks to generate userSig for a specific userID.
+- User needs a test credential for IM/TRTC local integration debugging.
 
-输入：
+When NOT to call:
+- User asks about userSig principles, production signing architecture, or security design.
+- User does not provide a concrete userID yet.
+
+Common trigger lexicon:
+- 生成 userSig, 测试凭证, 本地联调凭证, userID 对应 userSig, IM 登录凭证, TRTC 登录凭证
+
+Inputs:
 - userID
 
-返回：
-- content: [{ type: 'text', text: userSig 结果或错误说明 }]
+Outputs:
+- content: [{ type: 'text', text: userSig result or error details }]
 
-边界：
-- 面向已明确 userID 的测试凭证生成，不负责解释 userSig 原理、签发流程或生产鉴权方案
-- 仅用于开发测试
-- 生产环境应改为服务端签发
-- 如果环境变量缺失，需先补齐配置
+Boundaries:
+- This tool is for test credential generation only.
+- Production should use server-side signing.
+- If required environment variables are missing, return configuration guidance.
 `;
 export const GET_USERSIG_DEFINITION = {
     name: 'get_usersig',
     description: TOOL_DESCRIPTION,
     parameter_descriptions: {
-        userID: '登录腾讯云应用的 userID',
+        userID: 'Target userID for Tencent Cloud app login.',
     },
 };

package/tools/definitions/get_web_call_uikit_integration_def.js

@@ -1,26 +1,35 @@
 import { INTEGRATION_BOUNDARY_SUFFIX } from './integration-boundary.js';
 const TOOL_DESCRIPTION = `
-用途：
-返回 Web TUICallKit preset 集成文档，适合实现 PC/H5 音视频通话应用。
+Purpose:
+Return Web TUICallKit preset integration docs for explicit codegen implementation.
 
-典型适用问题：
+When to call (MUST):
+- User explicitly asks for runnable project integration code or concrete implementation steps.
+
+When NOT to call:
+- Pure feature Q&A, documentation lookup, API/component explanation, troubleshooting.
+
+Scope details:
+Returns Web TUICallKit preset integration documentation for PC/H5 audio-video calling applications.
+
+Common trigger lexicon:
 Web Call UIKit, Web TUICallKit, TUICallKit, preset 集成, React, Vue, PC, H5, 音视频通话, 视频通话, 语音通话, 集成, 呼叫, 接听
 
-输入：
+Inputs:
 - framework: react | vue
-- prompt: 用户的原始问题全文，保留完整上下文，不要压缩成关键词摘要
+- prompt: Original user question. Keep full context; do not compress into keyword summary.
 
-返回：
-- content: [{ type: 'text', text: 文档正文或说明文本 }]
+Outputs:
+- content: [{ type: 'text', text: Documentation body or explanatory text }]
 
-边界：
-- 当用户未明确平台或框架时，应先调用 'present_framework_choice'
-- 面向 Web CallKit preset 整体集成，不负责 API 细节或交互式框架选择
+Boundaries:
+- If platform/framework is not specified, call 'present_framework_choice' first.
+- Targets end-to-end Web CallKit preset integration, not API-level details or interactive framework selection.
 ${INTEGRATION_BOUNDARY_SUFFIX}
 `;
 const PARAMETER_DESCRIPTIONS = {
-    framework: '目标框架。参数名固定为 framework，禁止传 platform。可选值：react | vue。',
-    prompt: '用户的原始问题全文，保留完整上下文，不要压缩成关键词摘要。',
+    framework: 'Target framework. Parameter name must be framework (not platform). Allowed values: react | vue.',
+    prompt: 'Original user question. Keep full context; do not compress into keyword summary.',
 };
 export const GET_WEB_CALL_UIKIT_INTEGRATION_DEFINITION = {
     name: 'get_web_call_uikit_integration',

package/tools/definitions/get_web_chat_uikit_integration_def.js

@@ -1,28 +1,37 @@
 import { INTEGRATION_BOUNDARY_SUFFIX } from './integration-boundary.js';
 const TOOL_DESCRIPTION = `
-用途：
-返回 Web Chat UIKit 集成文档，适合实现完整聊天应用或单聊天窗口接入。
+Purpose:
+Return Web Chat UIKit integration docs for explicit codegen implementation.
 
-典型适用问题：
+When to call (MUST):
+- User explicitly asks for runnable project integration code or concrete implementation steps.
+
+When NOT to call:
+- Pure feature Q&A, documentation lookup, API/component explanation, troubleshooting.
+
+Scope details:
+Returns Web Chat UIKit integration documentation for full-featured chat app or chat-only widget embedding.
+
+Common trigger lexicon:
 Web Chat UIKit, TUIKit, IM, 聊天, 会话列表, 聊天窗口, React, Vue, full-featured, chat-only, 客服, 问诊, 消息入口
 
-输入：
+Inputs:
 - framework: react | vue
 - goals: [full-featured] | [chat-only]
-- prompt: 用户的原始问题全文，保留完整上下文，不要压缩成关键词摘要
+- prompt: Original user question. Keep full context; do not compress into keyword summary.
 
-返回：
-- content: [{ type: 'text', text: 文档正文或说明文本 }]
+Outputs:
+- content: [{ type: 'text', text: Documentation body or explanatory text }]
 
-边界：
-- 当用户未明确平台或框架时，应先调用 'present_framework_choice'
-- 面向 Web Chat UIKit 整体集成，不负责组件级细节或交互式框架选择
+Boundaries:
+- If platform/framework is not specified, call 'present_framework_choice' first.
+- Targets end-to-end Web Chat UIKit integration, not component-level details or interactive framework selection.
 ${INTEGRATION_BOUNDARY_SUFFIX}
 `;
 const PARAMETER_DESCRIPTIONS = {
-    framework: '目标框架。参数名固定为 framework，禁止传 platform。可选值：react | vue。',
-    goals: '功能目标数组。仅允许传一个值，可选值：full-featured（完整应用）| chat-only（单聊天窗口）。',
-    prompt: '用户的原始问题全文，保留完整上下文，不要压缩成关键词摘要。',
+    framework: 'Target framework. Parameter name must be framework (not platform). Allowed values: react | vue.',
+    goals: 'Goal list. Exactly one value is allowed: full-featured | chat-only.',
+    prompt: 'Original user question. Keep full context; do not compress into keyword summary.',
 };
 export const GET_WEB_CHAT_UIKIT_INTEGRATION_DEFINITION = {
     name: 'get_web_chat_uikit_integration',

package/tools/definitions/get_web_live_uikit_integration_def.js

@@ -1,25 +1,34 @@
 import { INTEGRATION_BOUNDARY_SUFFIX } from './integration-boundary.js';
 const TOOL_DESCRIPTION = `
-用途：
-返回 Web Live UIKit 页面级集成文档，适合接入直播列表页、观看页、开播页和连麦入口页。
+Purpose:
+Return Web Live UIKit integration docs for explicit codegen implementation.
 
-典型适用问题：
+When to call (MUST):
+- User explicitly asks for runnable project integration code or concrete implementation steps.
+
+When NOT to call:
+- Pure feature Q&A, documentation lookup, API/component explanation, troubleshooting.
+
+Scope details:
+Returns Web Live UIKit page-level integration documentation for live list, player, pusher, and co-guest entry pages.
+
+Common trigger lexicon:
 Web Live UIKit, TUILiveUIKit, Vue, 页面级集成, 页面接入, 列表页, 观看页, 开播页, liveList, livePlayer-desk, livePlayer-h5, livePusher
 
-输入：
-- goals: 功能列表
-- prompt: 用户的原始问题全文，保留完整上下文，不要压缩成关键词摘要
+Inputs:
+- goals: Feature list
+- prompt: Original user question. Keep full context; do not compress into keyword summary.
 
-返回：
-- content: [{ type: 'text', text: 文档正文或说明文本 }]
+Outputs:
+- content: [{ type: 'text', text: Documentation body or explanatory text }]
 
-边界：
-- 当前主要面向 Web Vue 页面级接入，不负责 State API 字段方法或单组件详解
+Boundaries:
+- Primarily targets Web Vue page-level integration, not State API field/method deep dives or single-component details.
 ${INTEGRATION_BOUNDARY_SUFFIX}
 `;
 const PARAMETER_DESCRIPTIONS = {
-    goals: '功能列表。可选值：liveList | livePlayer-desk | livePlayer-h5 | livePusher。',
-    prompt: '用户的原始问题全文，保留完整上下文，不要压缩成关键词摘要。',
+    goals: 'Goals list. Allowed values: liveList | livePlayer-desk | livePlayer-h5 | livePusher。',
+    prompt: 'Original user question. Keep full context; do not compress into keyword summary.',
 };
 export const GET_WEB_LIVE_UIKIT_INTEGRATION_DEFINITION = {
     name: 'get_web_live_uikit_integration',