@tencent-rtc/mcp 1.7.5 → 1.7.7

package/server-config.js

@@ -1,4 +1,5 @@
 import { reportESClient } from './utils/report-es-client.js';
+import { reportCLSClient } from './utils/report-cls-client.js';
 import { isValidSDKAppID } from './utils/is-valid-sdkappid.js';
 import { getDeviceIdentifier } from './utils/get-device-identifier.js';
 class ServerConfig {
@@ -16,17 +17,30 @@ class ServerConfig {
     parseEnvConfig() {
         const config = {};
         const { SDKAPPID, SECRETKEY } = process.env || {};
-        if (SDKAPPID) {
+        if (SDKAPPID && isValidSDKAppID(SDKAPPID)) {
             config.SDKAppID = SDKAPPID;
         }
-        const sdkappid = isValidSDKAppID(SDKAPPID) ? SDKAPPID : `${getDeviceIdentifier()}:en`;
-        reportESClient({
-            SDKAppID: sdkappid,
-            method: 'mcp_config'
-        });
+        else {
+            config.SDKAppID = `${getDeviceIdentifier()}:en`;
+        }
         if (SECRETKEY) {
             config.secretKey = SECRETKEY;
         }
+        try {
+            reportESClient({
+                SDKAppID: config.SDKAppID,
+                method: 'mcp_config'
+            });
+            reportCLSClient({
+                SDKAppID: config.SDKAppID,
+                method: 'mcp_server_config',
+                from: 'stdio',
+                info: JSON.stringify({
+                    status: 'success',
+                }),
+            });
+        }
+        catch { }
         return config;
     }
     getConfig() {

package/server.js

@@ -1,47 +1,53 @@
 import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
 import { registryTools } from './tools/index.js';
 const SERVER_INSTRUCTIONS = `
-You are using Tencent RTC MCP Server for SDK documentation retrieval.
+You are using Tencent RTC MCP Server for SDK documentation retrieval and integration guidance.
 
-- search_trtc_knowledge: Primary tool for searching Tencent RTC / Chat (IM) / Push (TIMPush) documentation.
-  Covers: Chat UIKit, CallKit, LiveKit, RoomKit, TRTC Native SDK, WebRTC/rtcEngine, TIMPush.
-  Use this tool FIRST for technical docs / FAQ / error codes / integration guide lookups.
-  Do NOT use web_search for questions answerable by this knowledge base.
+Tool routing rules (MUST):
+- search_trtc_knowledge is the default entry for technical consultation: docs lookup, API explanation, error troubleshooting, and integration guidance requests without explicit code generation intent.
+- get_*_integration tools are codegen-only. Call them only when user explicitly asks for runnable project integration code/implementation.
+- present_framework_choice is used only when platform/framework is required but missing.
+- Do not use web_search for questions answerable by this knowledge base.
 
-**Product routing (MUST infer product[] before calling search_trtc_knowledge):**
-- TIMPush / push / vendor channel / FCM / APNs / Huawei / Xiaomi / OPPO / vivo -> product=["push"] (independent product; do not misroute to chat)
-- conversation / TUIKit / ChatKit / Chat component / theme customization -> ["chat"]
-- CallKit / call -> ["call"]; live streaming / voice room / LiveKit -> ["live"]; RoomKit / conference -> ["room"]
+Product routing (MUST infer product[] before calling search_trtc_knowledge):
+- TIMPush / push / vendor channel / FCM / APNs / Huawei / Xiaomi / OPPO / vivo -> ["push"]
+- conversation / TUIKit / ChatKit / chat component / theme customization -> ["chat"]
+- CallKit / call -> ["call"]
+- live streaming / voice room / LiveKit -> ["live"]
+- RoomKit / conference -> ["room"]
 - TRTC Web SDK / rtcengine / WebRTC plugin -> ["rtcengine"]
 - TRTCCloud / Native SDK (client side) -> ["native_trtc_sdk"]
-- If both push and Chat are involved -> ["push","chat"]
-- If product cannot be uniquely inferred from prompt -> ask user to clarify first; do NOT hard-search with empty product; do NOT use web_search.
+- If both push and chat are involved -> ["push","chat"]
+- If product cannot be inferred, ask user to clarify first.
 
-**Frameworks:** If status=needs_framework, MUST call present_framework_choice first. See search_trtc_knowledge tool description decision table.
-**When in doubt:** still prefer search_trtc_knowledge with best-guess product; if status is empty or low_confidence, then clarify or retry.
+Framework policy:
+- If search_trtc_knowledge returns status=needs_framework, call present_framework_choice first.
+- For cross-platform product-level topics (pricing, REST API, webhook, console config), framework may be omitted.
 
-**queryID passing rules (hard rule; violation breaks CLS trace continuity):**
-- First search_trtc_knowledge call: no queryID required (defaults to empty); response JSON will include server-generated queryID.
-- Every subsequent call to search_trtc_knowledge / finalize_answer / submit_feedback: MUST carry the first returned queryID.
-- Missing queryID means a brand-new consultation (CLS data cannot be linked).
-- For multi-sub-question iterative searches, always reuse the same queryID.
+queryID passing rules (hard rule):
+- First search_trtc_knowledge call: queryID can be empty; server returns a queryID.
+- Every subsequent search_trtc_knowledge / finalize_answer / submit_feedback call in the same consultation MUST reuse that queryID.
+- Missing queryID creates a new consultation and breaks trace continuity.
 
-Workflow:
-1. Call search_trtc_knowledge. Reuse the same queryID for all retries/searches in this consultation.
-2. Draft the complete answer from fragments. Include References from meta.references/doc_urls when available.
-3. MUST call finalize_answer with the same prompt, answer, and queryID before replying.
-4. Reply with that answer + finalize_answer follow-up text.
-5. After finalize_answer follow-up, inspect the next user reply before any normal response. If it means Yes/resolved/thanks/OK, MUST call submit_feedback(resolved="1") before replying. If it means No/unresolved/still not working, MUST call submit_feedback(resolved="0") before replying. Never claim feedback was submitted unless submit_feedback was actually called.
+Consultation workflow (search_trtc_knowledge flow only):
+1. Call search_trtc_knowledge (reuse same queryID for retries).
+2. Draft answer from fragments and include references when available.
+3. MUST call finalize_answer with same prompt, answer, and queryID before replying.
+4. Reply with finalized answer only.
+5. If user gives explicit resolved/unresolved feedback after follow-up, MUST call submit_feedback before normal reply.
+
+Codegen workflow note:
+- For get_*_integration codegen flow, do NOT call finalize_answer or submit_feedback.
 
 User-visible output rules (MUST):
-- Internal routing/tool decisions are NEVER user-facing text.
-- Before calling any tool, do NOT output prefacing planning text such as “should call... / call ... first / let me search first / this is a consultation task / not codegen”.
-- If a tool call is needed, call it directly and then provide user-visible results only.
+- Internal routing/tool decisions are never user-facing text.
+- Do not output planning text like "I should call...", "let me search first", or "this is consultation not codegen".
+- If a tool call is needed, call it directly and then output final actionable content only.
 `.trim();
 export function createServer() {
     const server = new McpServer({
-        name: "Tencent RTC MCP Server",
-        version: "1.7.5",
+        name: 'Tencent RTC MCP Server',
+        version: '1.7.7',
     }, {
         instructions: SERVER_INSTRUCTIONS,
     });

package/tools/common/get_usersig.js

@@ -21,7 +21,7 @@ const registryGetUserSigTool = (mcpServer) => {
                         text: JSON.stringify({
                             error: 'CONFIG_MISSING',
                             message: 'Failed to generate userSig. Reason: SDKAppID or secretKey was not configured via MCP environment variables.',
-                            guide: 'Please guide the user to configure SDKAppID and secretKey according to the tool description (Constraints 2, 3, and 4), specifically by obtaining them from the IM or TRTC Console.'
+                            guide: 'Please guide the user to configure SDKAppID and secretKey in MCP environment variables, usually obtained from the IM or TRTC Console.'
                         }),
                     }
                 ]

package/tools/definitions/get_native_call_uikit_integration_def.js

@@ -3,24 +3,30 @@ const TOOL_DESCRIPTION = `
 Purpose:
 Return Native TUICallKit preset integration docs for setting up a complete mobile calling experience with a ready-made call UI.
 
-Typical use cases (shared triggers, may also match 'get_native_callkit_core_integration' Core tool):
+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 (shared triggers, may also match 'get_native_callkit_core_integration' Core tool):
 integrate CallKit, set up CallKit, audio/video call, voice call, video call, 1v1 call, group call, calling feature, make a call, answer a call, incoming call, offline push, VoIP
-When any of the shared triggers above match, **ask the user first**: "Do you want to integrate with the default call UI (TUICallKit preset), or build a custom call UI on top of the Core SDK?" If the user picks "default / preset", call this tool; if the user picks "custom / Core", call 'get_native_callkit_core_integration'.
+When any of the shared triggers above match, ask user first: "Do you want the default call UI (TUICallKit preset), or a custom call UI on top of the Core SDK?" If user picks default/preset, call this tool; if user picks custom/Core, call 'get_native_callkit_core_integration'.
 
-Typical use cases (preset exclusive triggers, only match this tool, no follow-up question needed):
+Scope details (preset exclusive triggers, only match this tool, no follow-up needed):
 TUICallKit, Native TUICallKit, Native Call UIKit, preset, preset integration, ready-made UI, default UI, default call UI, out-of-the-box call screen, prebuilt call page, TUICallKit Flutter, TUICallKit Android, TUICallKit iOS
 
-Input:
+Inputs:
 - framework: flutter | android | ios
 - prompt: The user's original question in full. Keep the full context. Do not compress it into keywords or a short summary.
 
-Returns:
-- content: [{ type: 'text', text: documentation content or explanatory text }]
+Outputs:
+- content: [{ type: 'text', text: Documentation body or explanatory text }]
 
 Boundaries:
 - If the user has not specified a platform or framework, call 'present_framework_choice' first.
 - When framework=uni-app, this tool is not supported (preset has no uni-app build). Call 'get_native_callkit_core_integration' instead.
-- When the user has already indicated "custom UI", "Core SDK", "AtomicXCore", "CallStore", or "build my own call page" or similar Core exclusive triggers, call 'get_native_callkit_core_integration' directly and do not route through this tool.
+- When the user has already indicated "custom UI", "Core SDK", "AtomicXCore", "CallStore", or "build my own call page" or similar Core-exclusive triggers, call 'get_native_callkit_core_integration' directly and do not route through this tool.
 - This tool is for Native CallKit preset integration. It is not for ringtone, virtual background, avatar, floating window, or other single-feature/API settings.
 ${INTEGRATION_BOUNDARY_SUFFIX}
 `;

package/tools/definitions/get_native_callkit_core_integration_def.js

@@ -1,58 +1,69 @@
 import { INTEGRATION_BOUNDARY_SUFFIX } from './integration-boundary.js';
 const TOOL_DESCRIPTION = `
 Purpose:
-Return Native CallKit Core base-integration docs based on the AtomicXCore SDK for developers who want a custom (no preset UI) call screen, covering make-call, answer-call, and offline-push.
+Return Native CallKit Core integration docs for explicit codegen implementation.
 
-Typical use cases (shared triggers, may also match 'get_native_call_uikit_integration' preset tool):
-integrate CallKit, set up CallKit, audio/video call, voice call, video call, 1v1 call, group call, calling feature, make a call, answer a call, incoming call, offline push, VoIP
-When any of the shared triggers above match, **ask the user first**: "Do you want to integrate with the default call UI (TUICallKit preset), or build a custom call UI on top of the Core SDK?" If the user picks "custom / Core", call this tool; if the user picks "default / preset", call 'get_native_call_uikit_integration'.
+When to call (MUST):
+- User explicitly asks for runnable project integration code or concrete implementation steps.
 
-Typical use cases (Core SDK exclusive triggers, only match this tool, no follow-up question needed):
-Core SDK, AtomicXCore, no UI, custom UI, custom call UI, build my own call page, not using the default UI, customize call style, CallStore, CallCoreView, DeviceStore
+When NOT to call:
+- Pure feature Q&A, documentation lookup, API/component explanation, troubleshooting.
 
-Input:
+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
+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-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: feature module list (make_call | answer_call | offline_push)
-- prompt: The user's original question in full. Keep the full context. Do not compress it into keywords or a short summary.
+- goals: Feature module list (make_call | answer_call | offline_push)
+- prompt: Original user question. Keep full context; do not compress into keyword summary.
 
-Returns:
-- content: [{ type: 'text', text: documentation content or explanatory text }]
+Outputs:
+- content: [{ type: 'text', text: Documentation body or explanatory text }]
 
 Boundaries:
-- If the user has not specified a platform or framework, call 'present_framework_choice' first.
-- When framework=uni-app, only this tool (Core SDK) is supported; there is no TUICallKit preset path for uni-app. **Do not** ask "default UI vs custom UI" after the user picks uni-app; call this tool directly.
-- When framework=uni-app and goals includes offline_push, this tool returns an explanatory fallback message (uni-app Core does not currently ship offline-push integration docs). Guide the user to the Android / iOS offline-push docs and integrate FCM / APNs via uni-app native plugins, or switch to the TUICallKit preset solution.
-- This tool covers the core/store-level base-integration main path (CallStore make/answer + offline push). It is not for beauty, virtual background, floating window, or picture-in-picture.
-- It returns Core SDK base-integration docs, not a full preset UIKit page template.
+- 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: 'Target platform. The parameter name must be framework. Do not use platform. Allowed values: android | ios | flutter | uni-app. Note: uni-app is only supported by this tool (Core SDK); there is no TUICallKit preset path for uni-app, so do not ask "default UI vs custom UI" when the user picks uni-app.',
-    goals: 'Feature list. Allowed values: make_call (make a call) | answer_call (answer a call) | offline_push (offline push). Multiple values are allowed, e.g. ["make_call", "answer_call"] for both. Note: when framework=uni-app and goals contains offline_push, this tool returns an explanatory fallback message instead of full docs (uni-app Core does not currently ship an offline-push integration sample).',
-    prompt: "The user's original question in full. Keep the full context. Do not compress it into keywords or a short summary.",
+    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 = `This document is based on the AtomicXCore SDK. Do NOT use UI-kit APIs such as TUILogin or TUICallKit.\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 Code Generation Constraints - AtomicXCore]
-This document uses the AtomicXCore SDK (no-UI integration). Generate code strictly based on the document content. Do NOT introduce any API not mentioned in the document.
+This document describes an AtomicXCore (no-UI) integration path.
+Generate code strictly from documented APIs only, and do NOT introduce undocumented classes or methods.
 
-Principle: If an API or class name never appears in this document, do not use it in the generated code.
+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 Does Not Yet Provide Offline Push Integration Samples
+# uni-app Core SDK 暂未提供离线推送集成示例
 
-## Current Status
-AtomicXCore for uni-app has not yet released offline push (FCM / APNs) integration docs or sample code.
+## Current status
+当前 AtomicXCore for uni-app 尚未发布配套的离线推送（FCM / APNs）集成文档与示例代码。
 
-## Recommended Approach
-- Refer to the Android platform \`callkit/core-sdk/android/offline-push.md\` and integrate FCM Data Messages via the uni-app native Android plugin mechanism.
-- Refer to the iOS platform \`callkit/core-sdk/ios/offline-push.md\` and integrate VoIP Push via the uni-app native iOS plugin mechanism.
-- If you prefer not to implement native plugins yourself, consider using the \`get_native_call_uikit_integration\` tool to integrate the TUICallKit preset solution, which has built-in offline push support for uni-app.
+## 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
-- Do not fabricate uni-app Core offline push code — it may be inconsistent with the official SDK behavior.
-- Do not paste Android / iOS offline push code directly into a uni-app project — it requires native plugin bridging.
+- 不要凭空生成 uni-app Core 的离线推送代码，可能与官方 SDK 行为不一致。
+- 不要把 Android / iOS 的离线推送代码原样塞进 uni-app 项目，需要走原生插件桥接。
 `;
 export const GET_NATIVE_CALLKIT_CORE_INTEGRATION_DEFINITION = {
     name: 'get_native_callkit_core_integration',

package/tools/definitions/get_native_chat_uikit_integration_def.js

@@ -3,16 +3,23 @@ const TOOL_DESCRIPTION = `
 Purpose:
 Return Native Chat UIKit integration docs for building either a full IM app or a single chat window on mobile.
 
-Typical use cases:
+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:
+
 Native Chat UIKit, TUIKit, IM, chat, conversation list, chat window, Flutter, Android, iOS, full-featured, chat-only, customer service chat, consultation chat
 
-Input:
+Inputs:
 - framework: flutter | android | ios
 - goals: [full-featured] | [chat-only]
 - prompt: The user's original question in full. Keep the full context. Do not compress it into keywords or a short summary.
 
-Returns:
-- content: [{ type: 'text', text: documentation content or explanatory text }]
+Outputs:
+- content: [{ type: 'text', text: Documentation body or explanatory text }]
 
 Boundaries:
 - If the user has not specified a platform or framework, call 'present_framework_choice' first.

package/tools/definitions/get_native_live_uikit_integration_def.js

@@ -1,34 +1,40 @@
 import { INTEGRATION_BOUNDARY_SUFFIX } from './integration-boundary.js';
 const TOOL_DESCRIPTION = `
 Purpose:
-Return Native video live streaming integration docs based on TUILiveKit's preset UI components, for AI to complete out-of-the-box mobile (Android / iOS) video live streaming integration and code generation. Covers the live list page (audience entry), host streaming page, and audience watching page — all preset components with complete interactive UI and business logic (e.g. AnchorPrepareView, live list waterfall view, etc.).
+Return Native video live streaming integration docs based on TUILiveKit preset UI components for out-of-the-box Android/iOS integration and code generation.
 
-Typical use cases (shared trigger words, may also match the 'get_native_livekit_core_integration' Core tool):
+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 (shared triggers, may also match 'get_native_livekit_core_integration' Core tool):
 integrate LiveKit, TUILiveKit, video live streaming, live broadcast, host streaming, audience watching, live list, host page, watch page, live room list, Android, iOS
-When a shared trigger word is matched, **proactively ask the user first**: "Would you like to quickly integrate with the default live streaming UI (TUILiveKit preset), or build a custom UI on top of Core SDK / AtomicXCore?" Call this tool only after the user chooses "default/preset"; call 'get_native_livekit_core_integration' if they choose "custom/Core".
+When shared triggers match, ask user first: "Do you want the default live UI (TUILiveKit preset), or a custom UI on top of Core SDK/AtomicXCore?" If user chooses default/preset, call this tool; if user chooses custom/Core, call 'get_native_livekit_core_integration'.
 
-Typical use cases (preset-only trigger words, match this tool exclusively, call directly without asking):
-TUILiveKit, Native TUILiveKit, Native Live UIKit, preset, preset integration, preset UI, preset host page, preset watch page, preset live list, default live streaming UI, out-of-the-box live streaming UI, ready-made streaming page, already have a live streaming UI, TUILiveKit Android, TUILiveKit iOS, AnchorPrepareView
+Scope details (preset-only triggers, match this tool directly):
+TUILiveKit, Native TUILiveKit, Native Live UIKit, preset, preset integration, preset UI, preset host page, preset watch page, preset live list, default live streaming UI, out-of-the-box live streaming UI, ready-made streaming page, TUILiveKit Android, TUILiveKit iOS, AnchorPrepareView
 
-Input:
+Inputs:
 - framework: android | ios
-- goals: feature module list (multi-select; results are organized in the order live_list → host_streaming → audience_streaming)
+- goals: feature module list (results are organized in order: live_list -> host_streaming -> audience_streaming)
 - prompt: The user's original question in full. Keep the full context. Do not compress it into keywords or a short summary.
 
-Returns:
-- content: [{ type: 'text', text: documentation body (common environment setup / dependency integration for all platforms, plus integration steps and code for the selected feature pages) }]
+Outputs:
+- content: [{ type: 'text', text: Documentation body or explanatory text }]
 
 Boundaries:
-- This tool is for **video live streaming (live)** scenarios only. Voice room (voice / audio room / seat) is **out of scope** — for that use 'get_native_livekit_core_integration' instead, or inform the user preset UI is not yet supported for voice room
-- framework only supports android | ios (TUILiveKit video live streaming preset UI has no flutter / uni-app docs yet — for that use 'get_native_livekit_core_integration' instead, or inform the user it is not supported)
-- If the user has not specified a platform, call 'present_framework_choice' first
-- If the user has explicitly indicated Core-specific trigger words such as "custom UI", "Core SDK", "AtomicXCore", "LiveCoreView", or "build my own live page", call 'get_native_livekit_core_integration' directly instead of this tool
-- Covers full page integration for host streaming / audience watching / live list only. Not responsible for co-guest, PK, gifts, barrage, beauty, or audio effects extensions (use 'search_trtc_knowledge' for those)
+- This tool is for video live streaming scenarios only. Voice room scenarios are out of scope and should use 'get_native_livekit_core_integration'.
+- framework supports android | ios only. For flutter / uni-app, route to 'get_native_livekit_core_integration' or explain unsupported preset path.
+- If the user has not specified a platform, call 'present_framework_choice' first.
+- If the user explicitly indicates Core-specific words such as "custom UI", "Core SDK", "AtomicXCore", "LiveCoreView", or "build my own live page", call 'get_native_livekit_core_integration' directly.
+- Covers host_streaming / audience_streaming / live_list page integration only. For co-guest, PK, gifts, barrage, beauty, or audio effects, use 'search_trtc_knowledge'.
 ${INTEGRATION_BOUNDARY_SUFFIX}
 `;
 const PARAMETER_DESCRIPTIONS = {
     framework: 'Target platform. The parameter name must be framework. Do not use platform. Allowed values: android | ios.',
-    goals: 'Feature list (multi-select). Allowed values: live_list (live list page, audience entry) | host_streaming (host streaming page) | audience_streaming (audience watching page). A complete mobile live streaming app usually needs live_list + host_streaming + audience_streaming.',
+    goals: 'Feature list (multi-select). Allowed values: live_list (live list page, audience entry) | host_streaming (host streaming page) | audience_streaming (audience watching page). A complete mobile live app usually needs all three.',
     prompt: "The user's original question in full. Keep the full context. Do not compress it into keywords or a short summary.",
 };
 export const GET_NATIVE_LIVE_UIKIT_INTEGRATION_DEFINITION = {

package/tools/definitions/get_native_livekit_core_integration_def.js

@@ -3,17 +3,24 @@ const TOOL_DESCRIPTION = `
 Purpose:
 Return Native LiveKit Core base-integration docs based on AtomicXCore SDK for publishing, viewing, and room-list flows in live streaming or voice room apps.
 
-Typical use cases:
+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:
+
 Native LiveKit Core, AtomicXCore, no-UI SDK, core SDK, live streaming, voice room, publish, watch, room list, Android, iOS, Flutter, live, voice, set up the base live flow, set up the base voice room flow
 
-Input:
+Inputs:
 - scenario: live | voice
 - framework: android | ios | flutter
 - goals: feature module list
 - prompt: The user's original question in full. Keep the full context. Do not compress it into keywords or a short summary.
 
-Returns:
-- content: [{ type: 'text', text: documentation content or explanatory text }]
+Outputs:
+- content: [{ type: 'text', text: Documentation body or explanatory text }]
 
 Boundaries:
 - If the user has not specified a platform or framework, call 'present_framework_choice' first.

package/tools/definitions/get_usersig_def.js

@@ -1,26 +1,33 @@
 const TOOL_DESCRIPTION = `
 Purpose:
-Generate a test userSig from the MCP environment variables SDKAppID and secretKey for local IM or TRTC testing.
+Generate a test userSig using SDKAppID and secretKey from MCP environment variables, for IM/TRTC local debugging.
 
-Typical use cases:
-generate a userSig for a specific userID, create a test credential, local debugging credential, userSig for this userID, SDKAppID, secretKey, IM login credential, TRTC login credential
+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.
 
-Input:
+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:
+- generate userSig, test credential, local debug credential, userSig for userID, IM login credential, TRTC login credential
+
+Inputs:
 - userID
 
-Returns:
-- content: [{ type: 'text', text: userSig result or an error message }]
+Outputs:
+- content: [{ type: 'text', text: userSig result or error details }]
 
 Boundaries:
-- Use this tool only when the userID is already known and you need a test credential.
-- It does not explain userSig principles, issuing flow, or production authentication design.
-- It is for development and testing only.
-- Production systems should issue userSig from a server.
+- 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: 'The userID used to log in to the Tencent Cloud application.',
+        userID: 'Target userID for Tencent Cloud app login.',
     },
 };

package/tools/definitions/get_web_call_uikit_integration_def.js

@@ -3,15 +3,22 @@ const TOOL_DESCRIPTION = `
 Purpose:
 Return Web TUICallKit preset integration docs for setting up a complete calling experience on PC or H5.
 
-Typical use cases:
+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:
+
 Web Call UIKit, Web TUICallKit, TUICallKit, preset integration, React, Vue, PC, H5, audio/video calling, video call, voice call, integrate CallKit, calling flow, answering flow
 
-Input:
+Inputs:
 - framework: react | vue
 - prompt: The user's original question in full. Keep the full context. Do not compress it into keywords or a short summary.
 
-Returns:
-- content: [{ type: 'text', text: documentation content or explanatory text }]
+Outputs:
+- content: [{ type: 'text', text: Documentation body or explanatory text }]
 
 Boundaries:
 - If the user has not specified a platform or framework, call 'present_framework_choice' first.

package/tools/definitions/get_web_chat_uikit_integration_def.js

@@ -3,16 +3,23 @@ const TOOL_DESCRIPTION = `
 Purpose:
 Return Web Chat UIKit integration docs for building either a full chat app or a single chat window.
 
-Typical use cases:
+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:
+
 Web Chat UIKit, TUIKit, IM, chat, conversation list, chat window, React, Vue, full-featured, chat-only, customer service chat, consultation chat, message entry
 
-Input:
+Inputs:
 - framework: react | vue
 - goals: [full-featured] | [chat-only]
 - prompt: The user's original question in full. Keep the full context. Do not compress it into keywords or a short summary.
 
-Returns:
-- content: [{ type: 'text', text: documentation content or explanatory text }]
+Outputs:
+- content: [{ type: 'text', text: Documentation body or explanatory text }]
 
 Boundaries:
 - If the user has not specified a platform or framework, call 'present_framework_choice' first.

package/tools/definitions/get_web_live_uikit_integration_def.js

@@ -3,15 +3,22 @@ const TOOL_DESCRIPTION = `
 Purpose:
 Return Web Live UIKit page-level integration docs for wiring live list, player, publish, and co-guest entry pages.
 
-Typical use cases:
+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:
+
 Web Live UIKit, TUILiveUIKit, Vue, page-level integration, wire the live pages, set up the live list page, set up the player page, set up the publish page, liveList, livePlayer-desk, livePlayer-h5, livePusher
 
-Input:
+Inputs:
 - goals: feature list
 - prompt: The user's original question in full. Keep the full context. Do not compress it into keywords or a short summary.
 
-Returns:
-- content: [{ type: 'text', text: documentation content or explanatory text }]
+Outputs:
+- content: [{ type: 'text', text: Documentation body or explanatory text }]
 
 Boundaries:
 - This tool is primarily for Web Vue page-level integration. It is not for State API fields/methods or single-component deep dives.

package/tools/definitions/get_web_room_core_integration_def.js

@@ -3,29 +3,32 @@ const TOOL_DESCRIPTION = `
 Purpose:
 Return Web RoomKit Atomicx Core integration docs for building a custom meeting room without preset UI, covering login, room state, and device capabilities.
 
-Shared trigger phrases (may also match the preset tool \`get_web_room_uikit_integration\`):
+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 (shared triggers, may also match 'get_web_room_uikit_integration' preset tool):
 Web RoomKit, TUIRoomKit, Atomicx, Vue, integrate RoomKit, meeting room, room, meeting
-If the user only hits these shared trigger phrases, ask first:
-"Do you want the preset UI for quick integration (TUIRoomUIKit preset), or a custom room built on Atomicx APIs?"
-If the user chooses custom / Atomicx / Core, call this tool.
-If the user chooses preset / default UI, call \`get_web_room_uikit_integration\`.
+When user only hits shared triggers, ask first: "Do you want the preset UI for quick integration (TUIRoomUIKit), or a custom room built on Atomicx APIs?" If user chooses custom/Atomicx/Core, call this tool. If user chooses preset/default UI, call 'get_web_room_uikit_integration'.
 
-Core-only trigger phrases (call directly, no follow-up needed):
+Scope details (Core-only triggers, call directly):
 Atomicx API, custom meeting room, custom room UI, without preset UI, useRoomState, useDeviceState, useLoginState, room-state, device-state, device-detection
 
-Input:
+Inputs:
 - framework: vue
 - goals: room-state | device-detection | device-state
 - prompt: The user's original question in full. Keep the full context. Do not compress it into keywords or a short summary.
 
-Returns:
-- content: [{ type: 'text', text: documentation content or explanatory text }]
+Outputs:
+- content: [{ type: 'text', text: Documentation body or explanatory text }]
 
 Boundaries:
-- If the user has not specified a platform or framework, call \`present_framework_choice\` first.
-- This is for Atomicx Core integration only (login + room-state / device modules), not preset UI page templates.
-- Screen sharing, virtual background, scheduled meeting, and other advanced modules -> call \`search_trtc_knowledge(types=[feature])\`.
-- **Login constraint**: MUST call \`get_usersig\` to get a UserSig, then use \`useLoginState.login\`; never implement local UserSig generation such as GenerateTestUserSig inside the project.
+- If the user has not specified a platform or framework, call 'present_framework_choice' first.
+- This is for Atomicx Core integration only (login + room-state/device modules), not preset UI page templates.
+- Screen sharing, virtual background, scheduled meeting, and other advanced modules -> call 'search_trtc_knowledge(types=[feature])'.
+- Login constraint: MUST call 'get_usersig' to get a UserSig, then use useLoginState.login; never implement local UserSig generation such as GenerateTestUserSig inside the project.
 ${INTEGRATION_BOUNDARY_SUFFIX}
 `;
 const PARAMETER_DESCRIPTIONS = {