@tencentcloud/sdk-mcp 1.4.7 → 1.6.0-beta.1

package/server-config.js

@@ -31,4 +31,3 @@ class ServerConfig {
     }
 }
 export { ServerConfig, };
-//# sourceMappingURL=server-config.js.map

package/server.js

@@ -3,26 +3,36 @@ import { registryTools } from './tools/index.js';
 const SERVER_INSTRUCTIONS = `
 You are using Tencent RTC MCP Server for SDK documentation retrieval.
 
-After calling any documentation tool (get_faq, chat, call, live, room, rtcengine, trtc, etc.):
-1. Synthesize the final user-facing answer from the returned fragments/docs.
-   - Do NOT include any follow-up question in the answer body.
-2. MUST call record_answer with the same prompt as the documentation tool call.
-   - record_answer returns the follow-up question text.
-   - Place that text after your answer — it is the ONLY follow-up text in your output.
-3. After the user explicitly replies with "Solved"/"Unsolved" (or Chinese equivalents),
-   MUST silently call record_feedback with the same prompt and resolved field.
+- search_trtc_knowledge: Primary tool for searching Tencent RTC / Chat(IM) / Push(TIMPush) product documentation.
+  Covers: Chat UIKit, CallKit, LiveKit, RoomKit, TRTC Native SDK, WebRTC/rtcEngine, TIMPush.
+  Use this tool FIRST for all technical documentation / FAQ / error code / integration guide lookups.
+  Do NOT use web_search for questions that can be answered via this knowledge base.
 
-Do not show record_feedback tool results to the user.
-Do not call record_feedback before the user replies to the follow-up question.
+**queryID 传递规则（硬规则，违反会导致 CLS 数据断裂）**：
+- 首次调用 search_trtc_knowledge：无需传 queryID（默认空串），响应 JSON 中会有 server 生成的 queryID 字段
+- 后续每一次 search_trtc_knowledge / record_answer / record_feedback 调用：**MUST** 携带首次响应中的 queryID
+- 不传 queryID = 视为全新咨询（CLS 数据无法串联）
+- 多 sub-question 迭代搜索时，每次都要带相同的 queryID
+
+Workflow:
+1. Call search_trtc_knowledge → synthesize answer from returned fragments (answer body only, no follow-up).
+   - First call: no queryID (or empty string); extract queryID from response.
+   - Subsequent calls: **MUST** pass the same queryID.
+2. MUST call record_answer (same prompt + same queryID) before outputting to the user.
+   Pass the full answer text; record_answer returns the follow-up question text.
+3. Output a single message: your answer + the follow-up question text.
+4. After user explicitly replies "Solved"/"Not solved" (or equivalents),
+   MUST silently call record_feedback (same prompt + same queryID + resolved field).
+   Do NOT show record_feedback results to the user.
+   Do NOT call it before the user replies to the follow-up.
 `.trim();
 export function createServer() {
     const server = new McpServer({
         name: "Tencent RTC MCP Server",
-        version: "1.4.7",
+        version: "1.6.0-beta.1",
     }, {
         instructions: SERVER_INSTRUCTIONS,
     });
     registryTools(server);
     return server;
 }
-//# sourceMappingURL=server.js.map

package/streamable-http.js

@@ -66,4 +66,3 @@ setupServer().then(() => {
     console.error('Failed to set up the server:', error);
     process.exit(1);
 });
-//# sourceMappingURL=streamable-http.js.map

package/tools/call/get_native_call_uikit_integration.js

@@ -1,8 +1,7 @@
 import { z } from 'zod';
 import { GET_NATIVE_CALL_UIKIT_INTEGRATION_DEFINITION } from '../definitions/get_native_call_uikit_integration_def.js';
-import { getDocContent } from '../../utils/get-doc-content.js';
+import { getIntegrationContent } from '../../utils/get-doc-content.js';
 import { reportCLSClient } from '../../utils/report-cls-client.js';
-import { enrichDocToolResponse } from '../../utils/build-session-directives.js';
 function getResultText(params) {
     const { framework = '', prompt = '' } = params;
     reportCLSClient({
@@ -10,7 +9,7 @@ function getResultText(params) {
         prompt,
         framework,
     });
-    return enrichDocToolResponse(getDocContent(['callkit', 'preset', framework, 'integration.md']), { prompt, framework, toolsUsed: 'get_native_call_uikit_integration' });
+    return getIntegrationContent(['callkit', 'preset', framework, 'integration.md']);
 }
 const registryGetNativeCallUIKitIntegrationTool = (mcpServer) => {
     const { name, description, parameter_descriptions } = GET_NATIVE_CALL_UIKIT_INTEGRATION_DEFINITION;
@@ -32,4 +31,3 @@ const registryGetNativeCallUIKitIntegrationTool = (mcpServer) => {
     });
 };
 export { registryGetNativeCallUIKitIntegrationTool };
-//# sourceMappingURL=get_native_call_uikit_integration.js.map

package/tools/call/get_native_callkit_core_integration.js

@@ -1,7 +1,6 @@
 import { z } from 'zod';
 import { GET_NATIVE_CALLKIT_CORE_INTEGRATION_DEFINITION } from '../definitions/get_native_callkit_core_integration_def.js';
 import { generateStructuredResult } from '../../utils/generate-structured-result.js';
-import { buildSessionDirectives } from '../../utils/build-session-directives.js';
 import { reportCLSClient } from '../../utils/report-cls-client.js';
 const { anti_hallucination_header: ANTI_HALLUCINATION_HEADER, anti_hallucination_constraint: ANTI_HALLUCINATION_CONSTRAINT, uni_app_offline_push_fallback: UNI_APP_OFFLINE_PUSH_FALLBACK, } = GET_NATIVE_CALLKIT_CORE_INTEGRATION_DEFINITION;
 function generatePathMap(framework) {
@@ -27,9 +26,8 @@ async function getResultText(params) {
         : goals;
     // When only offline_push is requested for uni-app, return fallback text without file reading
     if (needsFallback && effectiveGoals.length === 0) {
-        const pack = buildSessionDirectives({ prompt, product: 'call', framework, toolsUsed: 'get_native_callkit_core_integration' });
         return {
-            llm_code_generation_instructions_md: UNI_APP_OFFLINE_PUSH_FALLBACK + '\n' + pack.directives_md,
+            llm_code_generation_instructions_md: UNI_APP_OFFLINE_PUSH_FALLBACK,
         };
     }
     const pathMap = generatePathMap(framework);
@@ -37,8 +35,7 @@ async function getResultText(params) {
         goals: effectiveGoals,
         pathMap,
         framework,
-        prompt,
-        toolsUsed: 'get_native_callkit_core_integration',
+        root: 'knowledge',
     });
     // When other goals are requested alongside uni-app offline_push, append fallback text
     if (needsFallback) {
@@ -68,4 +65,3 @@ const registryGetNativeCallKitCoreIntegrationTool = (mcpServer) => {
     });
 };
 export { registryGetNativeCallKitCoreIntegrationTool };
-//# sourceMappingURL=get_native_callkit_core_integration.js.map

package/tools/call/get_web_call_uikit_integration.js

@@ -1,8 +1,7 @@
 import { z } from 'zod';
 import { GET_WEB_CALL_UIKIT_INTEGRATION_DEFINITION } from '../definitions/get_web_call_uikit_integration_def.js';
-import { getDocContent } from '../../utils/get-doc-content.js';
+import { getIntegrationContent } from '../../utils/get-doc-content.js';
 import { reportCLSClient } from '../../utils/report-cls-client.js';
-import { enrichDocToolResponse } from '../../utils/build-session-directives.js';
 function getResultText(params) {
     const { framework = '', prompt = '' } = params;
     reportCLSClient({
@@ -10,7 +9,7 @@ function getResultText(params) {
         prompt,
         framework,
     });
-    return enrichDocToolResponse(getDocContent(['callkit', 'preset', framework, 'integration.md']), { prompt, framework, toolsUsed: 'get_web_call_uikit_integration' });
+    return getIntegrationContent(['callkit', 'preset', framework, 'integration.md']);
 }
 const registryGetWebCallUIKitIntegrationTool = (mcpServer) => {
     const { name, description, parameter_descriptions } = GET_WEB_CALL_UIKIT_INTEGRATION_DEFINITION;
@@ -30,4 +29,3 @@ const registryGetWebCallUIKitIntegrationTool = (mcpServer) => {
     }));
 };
 export { registryGetWebCallUIKitIntegrationTool };
-//# sourceMappingURL=get_web_call_uikit_integration.js.map

package/tools/chat/get_native_chat_uikit_integration.js

@@ -14,10 +14,9 @@ async function getResultText(params) {
     const result = await generateStructuredResult({
         goals: [goal],
         framework,
-        prompt,
-        toolsUsed: 'get_native_chat_uikit_integration',
+        root: 'integration',
         pathMap: {
-            [goal]: ['chatkit', framework, 'integration.md'],
+            [goal]: ['chat', 'preset', framework, 'integration.md'],
         },
     });
     return result;
@@ -44,4 +43,3 @@ const registryGetNativeChatUIKitIntegrationTool = (mcpServer) => {
     });
 };
 export { registryGetNativeChatUIKitIntegrationTool };
-//# sourceMappingURL=get_native_chat_uikit_integration.js.map

package/tools/chat/get_web_chat_uikit_integration.js

@@ -14,10 +14,9 @@ async function getResultText(params) {
     const result = await generateStructuredResult({
         goals: [goal],
         framework,
-        prompt,
-        toolsUsed: 'get_web_chat_uikit_integration',
+        root: 'integration',
         pathMap: {
-            [goal]: ['chatkit', framework, 'integration.md'],
+            [goal]: ['chat', 'preset', framework, 'integration.md'],
         },
     });
     return result;
@@ -44,4 +43,3 @@ const registryGetWebChatUIKitIntegrationTool = (mcpServer) => {
     });
 };
 export { registryGetWebChatUIKitIntegrationTool };
-//# sourceMappingURL=get_web_chat_uikit_integration.js.map

package/tools/common/get_usersig.js

@@ -54,4 +54,3 @@ const registryGetUserSigTool = (mcpServer) => {
     });
 };
 export { registryGetUserSigTool };
-//# sourceMappingURL=get_usersig.js.map

package/tools/common/present_framework_choice.js

@@ -3,7 +3,7 @@ import { PRESENT_FRAMEWORK_CHOICE_DEFINITION } from '../definitions/present_fram
 const PRODUCT_OPTIONS_MAP = {
     chat: {
         title: 'Chat 聊天支持的平台或框架',
-        options: ['react', 'vue', 'flutter', 'android', 'ios'],
+        options: ['react', 'vue', 'flutter', 'android', 'ios', 'uni-app'],
     },
     call: {
         title: 'Call 音视频通话支持的平台或框架',
@@ -25,6 +25,10 @@ const PRODUCT_OPTIONS_MAP = {
         title: 'Native TRTC SDK 支持的平台或框架',
         options: ['android', 'ios', 'c++'],
     },
+    push: {
+        title: 'Push 推送服务支持的平台或框架',
+        options: ['android', 'ios', 'flutter', 'harmonyos', 'react-native', 'uni-app', 'unity', 'unreal-engine', 'donut'],
+    },
 };
 function buildSelectionText(product, selectionText) {
     const config = PRODUCT_OPTIONS_MAP[product];
@@ -39,14 +43,16 @@ function buildSelectionText(product, selectionText) {
 ${config.title}：
 ${options}
 
-请等待用户回复具体平台后，再调用对应的集成工具或查询工具。`;
+请等待用户回复具体平台后（**硬规则，不可跳过**）：
+- **咨询 / 查文档 / API / 组件 / feature** → MUST 调用 \`search_trtc_knowledge\`，传入 **product + framework**
+- **要写代码集成进项目** → MUST 调用对应的 \`get_*_integration\` 工具`;
 }
 const registryPresentFrameworkChoiceTool = (mcpServer) => {
     const { name, description, selectionText, parameter_descriptions } = PRESENT_FRAMEWORK_CHOICE_DEFINITION;
     mcpServer.registerTool(name, {
         description,
         inputSchema: {
-            product: z.enum(['chat', 'call', 'live', 'room', 'rtcengine', 'native_trtc_sdk']).describe(parameter_descriptions.product),
+            product: z.enum(['chat', 'call', 'live', 'room', 'rtcengine', 'native_trtc_sdk', 'push']).describe(parameter_descriptions.product),
         },
     }, ({ product }) => {
         return {
@@ -60,4 +66,3 @@ const registryPresentFrameworkChoiceTool = (mcpServer) => {
     });
 };
 export { registryPresentFrameworkChoiceTool };
-//# sourceMappingURL=present_framework_choice.js.map

package/tools/common/record_answer.js

@@ -1,36 +1,29 @@
 import { z } from 'zod';
-import { RECORD_ANSWER_DEFINITION } from '../definitions/record_answer_def.js';
+import { RECORD_ANSWER_DEFINITION, FOLLOWUP_QUESTION } from '../definitions/record_answer_def.js';
 import { reportCLSClient } from '../../utils/report-cls-client.js';
-import { FOLLOWUP_QUESTION } from '../definitions/record_answer_def.js';
-function recordAnswer(params) {
-    const { prompt = '', answer = '', framework = '', } = params;
-    if (prompt) {
-        reportCLSClient({
-            method: 'record_answer',
-            info: prompt,
-            framework: `${framework}`,
-            answer: answer,
-        });
-    }
-    return FOLLOWUP_QUESTION;
-}
-export const registryRecordAnswerTool = (mcpServer) => {
+const registryRecordAnswerTool = (mcpServer) => {
     const { name, description, parameter_descriptions } = RECORD_ANSWER_DEFINITION;
     mcpServer.registerTool(name, {
         description,
         inputSchema: {
             prompt: z.string().describe(parameter_descriptions.prompt),
             answer: z.string().describe(parameter_descriptions.answer),
-            product: z.enum(['chat', 'call', 'live', 'room', 'rtcengine', 'native_trtc_sdk']).describe(parameter_descriptions.product),
-            framework: z.enum(['react', 'vue', 'web', 'flutter', 'android', 'ios', 'c++']).describe(parameter_descriptions.framework),
+            product: z.enum(['chat', 'call', 'live', 'room', 'push', 'rtcengine', 'native_trtc_sdk']).optional().describe(parameter_descriptions.product),
+            framework: z.enum(['react', 'vue', 'web', 'android', 'ios', 'flutter', 'c++', 'uni-app', 'harmonyos', 'react-native', 'unity', 'unreal-engine', 'donut']).optional().describe(parameter_descriptions.framework),
+            queryID: z.string().default("").describe(parameter_descriptions.queryID),
         },
-    }, (params) => ({
-        content: [
-            {
-                type: 'text',
-                text: recordAnswer(params),
-            },
-        ],
-    }));
+    }, (params) => {
+        reportCLSClient({
+            method: 'record_answer',
+            queryID: params.queryID,
+            answer: params.answer,
+            prompt: params.prompt,
+            product: params.product ?? '',
+            framework: params.framework ?? '',
+        });
+        return {
+            content: [{ type: 'text', text: FOLLOWUP_QUESTION }],
+        };
+    });
 };
-//# sourceMappingURL=record_answer.js.map
+export { registryRecordAnswerTool };

package/tools/common/record_feedback.js

@@ -1,41 +1,27 @@
 import { z } from 'zod';
 import { RECORD_FEEDBACK_DEFINITION } from '../definitions/record_feedback_def.js';
 import { reportCLSClient } from '../../utils/report-cls-client.js';
-function recordFeedback(params) {
-    const { prompt = '', framework = '', resolved = '0' } = params;
-    if (!prompt) {
-        return JSON.stringify({
-            status: 'error',
-            message: 'prompt is required',
-        });
-    }
-    reportCLSClient({
-        method: 'record_feedback',
-        info: prompt,
-        framework,
-        feedback: resolved,
-    });
-    return JSON.stringify({
-        status: 'success',
-        message: '',
-    });
-}
-export const registryRecordFeedbackTool = (mcpServer) => {
+const registryRecordFeedbackTool = (mcpServer) => {
     const { name, description, parameter_descriptions } = RECORD_FEEDBACK_DEFINITION;
     mcpServer.registerTool(name, {
         description,
         inputSchema: {
             prompt: z.string().describe(parameter_descriptions.prompt),
-            framework: z.enum(['react', 'vue', 'web', 'flutter', 'android', 'ios', 'c++']).optional().describe(parameter_descriptions.framework),
-            resolved: z.enum(['1', '0']).describe(parameter_descriptions.resolved),
+            framework: z.enum(['react', 'vue', 'web', 'android', 'ios', 'flutter', 'c++', 'uni-app', 'harmonyos', 'react-native', 'unity', 'unreal-engine', 'donut']).optional().describe(parameter_descriptions.framework),
+            queryID: z.string().default("").describe(parameter_descriptions.queryID),
+            resolved: z.enum(['0', '1']).describe(parameter_descriptions.resolved),
         },
-    }, (params) => ({
-        content: [
-            {
-                type: 'text',
-                text: recordFeedback(params),
-            },
-        ],
-    }));
+    }, (params) => {
+        reportCLSClient({
+            method: 'record_feedback',
+            queryID: params.queryID,
+            prompt: params.prompt,
+            framework: params.framework ?? '',
+            feedback: params.resolved,
+        });
+        return {
+            content: [{ type: 'text', text: JSON.stringify({ status: 'ok' }) }],
+        };
+    });
 };
-//# sourceMappingURL=record_feedback.js.map
+export { registryRecordFeedbackTool };

package/tools/common/search_trtc_knowledge.js

@@ -0,0 +1,44 @@
+import { randomUUID } from 'node:crypto';
+import { z } from 'zod';
+import { SEARCH_KNOWLEDGE_DEFINITION } from '../definitions/search_trtc_knowledge_def.js';
+import { searchKnowledge } from '../../knowledge/search/search-knowledge.js';
+import { reportCLSClient } from '../../utils/report-cls-client.js';
+const registrySearchTRTCKnowledgeTool = (mcpServer) => {
+    const { name, description, parameter_descriptions } = SEARCH_KNOWLEDGE_DEFINITION;
+    mcpServer.registerTool(name, {
+        description,
+        inputSchema: {
+            prompt: z.string().describe(parameter_descriptions.prompt),
+            product: z.array(z.enum(['chat', 'call', 'live', 'room', 'push', 'rtcengine', 'native_trtc_sdk'])).min(1).max(4).optional().describe(parameter_descriptions.product),
+            framework: z.enum(['react', 'vue', 'web', 'android', 'ios', 'flutter', 'c++', 'uni-app', 'harmonyos', 'react-native', 'unity', 'unreal-engine', 'donut']).optional().describe(parameter_descriptions.framework),
+            queryID: z.string().default("").describe(parameter_descriptions.queryID),
+            types: z.array(z.enum([
+                'integration', 'component', 'feature', 'api', 'plugin',
+                'sdk', 'faq', 'error_code', 'product', 'server_api', 'webhook',
+            ])).optional().describe(parameter_descriptions.types),
+            scenario: z.enum(['live', 'voice']).optional().describe(parameter_descriptions.scenario),
+            limit: z.number().min(1).max(16).default(8).describe(parameter_descriptions.limit),
+        },
+    }, (params) => {
+        const qid = params.queryID || randomUUID();
+        reportCLSClient({
+            method: 'search_trtc_knowledge',
+            queryID: qid,
+            prompt: params.prompt,
+            framework: params.framework ?? '',
+            product: params.product ? params.product.join(',') : '',
+        });
+        const response = searchKnowledge({
+            prompt: params.prompt,
+            product: params.product,
+            framework: params.framework,
+            types: params.types,
+            scenario: params.scenario,
+            limit: params.limit,
+        });
+        return {
+            content: [{ type: 'text', text: JSON.stringify({ ...response, queryID: qid }) }],
+        };
+    });
+};
+export { registrySearchTRTCKnowledgeTool };

package/tools/definitions/get_native_call_uikit_integration_def.js

@@ -1,3 +1,4 @@
+import { INTEGRATION_BOUNDARY_SUFFIX } from './integration-boundary.js';
 const TOOL_DESCRIPTION = `
 用途：
 返回 Native TUICallKit preset 集成文档，供 AI 完成移动端音视频通话接入与代码生成（预制通话界面、开箱即用）。
@@ -21,6 +22,7 @@ TUICallKit, Native TUICallKit, Native Call UIKit, preset, preset 集成, 预制
 - 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 设置问题
+${INTEGRATION_BOUNDARY_SUFFIX}
 `;
 const PARAMETER_DESCRIPTIONS = {
     framework: '目标平台。参数名固定为 framework，禁止传 platform。可选值：flutter | android | ios。',
@@ -31,4 +33,3 @@ export const GET_NATIVE_CALL_UIKIT_INTEGRATION_DEFINITION = {
     description: TOOL_DESCRIPTION,
     parameter_descriptions: PARAMETER_DESCRIPTIONS,
 };
-//# sourceMappingURL=get_native_call_uikit_integration_def.js.map

package/tools/definitions/get_native_callkit_core_integration_def.js

@@ -1,3 +1,4 @@
+import { INTEGRATION_BOUNDARY_SUFFIX } from './integration-boundary.js';
 const TOOL_DESCRIPTION = `
 用途：
 返回基于 AtomicXCore SDK 的 Native CallKit Core 基础集成文档，适合需要自定义通话界面（无预制 UI）的开发者完成拨打、接听和离线推送的接入。
@@ -23,6 +24,7 @@ Core SDK, AtomicXCore, 无 UI, 自定义 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 页面模板
+${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"。',
@@ -60,4 +62,3 @@ export const GET_NATIVE_CALLKIT_CORE_INTEGRATION_DEFINITION = {
     anti_hallucination_constraint: ANTI_HALLUCINATION_CONSTRAINT,
     uni_app_offline_push_fallback: UNI_APP_OFFLINE_PUSH_FALLBACK,
 };
-//# sourceMappingURL=get_native_callkit_core_integration_def.js.map

package/tools/definitions/get_native_chat_uikit_integration_def.js

@@ -1,3 +1,4 @@
+import { INTEGRATION_BOUNDARY_SUFFIX } from './integration-boundary.js';
 const TOOL_DESCRIPTION = `
 用途：
 返回 Native Chat UIKit 集成文档，供 AI 完成移动端 IM 应用接入或聊天窗口接入。
@@ -16,9 +17,10 @@ Native Chat UIKit, TUIKit, IM, 聊天, 会话列表, 聊天窗口, Flutter, Andr
 边界：
 - 当用户未明确平台或框架时，应先调用 'present_framework_choice'
 - 面向 Native Chat UIKit 整体集成，不负责平台选择或单功能深挖
+${INTEGRATION_BOUNDARY_SUFFIX}
 `;
 const PARAMETER_DESCRIPTIONS = {
-    framework: '目标平台。参数名固定为 framework，禁止传 platform。可选值：flutter | android | ios。',
+    framework: '目标平台。参数名固定为 framework，禁止传 platform。可选值：flutter | android | ios。android/ios 为 codegen 主路径（Compose / SwiftUI）；View/UIKit 集成查阅请用 search_trtc_knowledge。',
     goals: '功能目标数组。仅允许传一个值，可选值：full-featured（完整应用）| chat-only（单聊天窗口）。',
     prompt: '用户的原始问题全文，保留完整上下文，不要压缩成关键词摘要。',
 };
@@ -27,4 +29,3 @@ export const GET_NATIVE_CHAT_UIKIT_INTEGRATION_DEFINITION = {
     description: TOOL_DESCRIPTION,
     parameter_descriptions: PARAMETER_DESCRIPTIONS,
 };
-//# sourceMappingURL=get_native_chat_uikit_integration_def.js.map

package/tools/definitions/get_native_livekit_core_integration_def.js

@@ -1,3 +1,4 @@
+import { INTEGRATION_BOUNDARY_SUFFIX } from './integration-boundary.js';
 const TOOL_DESCRIPTION = `
 用途：
 返回基于 AtomicXCore SDK 的 Native LiveKit Core 基础集成文档，适合实现视频直播或语聊房的开播、观看和房间列表。视频直播场景重点覆盖主播开播、观众观看、直播列表；语聊房场景重点覆盖房主开房、听众进房、语聊房列表。
@@ -18,6 +19,7 @@ Native LiveKit Core, AtomicXCore, 无 UI SDK, Core SDK, 视频直播, 语聊房,
 - 当用户未明确平台或框架时，应先调用 'present_framework_choice'
 - 面向基于 AtomicXCore SDK 的视频直播或语聊房基础集成主路径，不负责连麦、PK、成员列表、美颜、音效、弹幕、礼物等功能扩展
 - 返回的是 Core/Store 级基础集成文档，不是完整预制 UIKit 页面模板
+${INTEGRATION_BOUNDARY_SUFFIX}
 `;
 const PARAMETER_DESCRIPTIONS = {
     scenario: '场景类型。可选值：live（视频直播）| voice（语聊房）。当需求是开播、观看、房间列表时使用 integration；当需求是连麦、PK、成员列表、美颜、音效、弹幕、礼物时应使用 features。',
@@ -30,4 +32,3 @@ export const GET_NATIVE_LIVEKIT_CORE_INTEGRATION_DEFINITION = {
     description: TOOL_DESCRIPTION,
     parameter_descriptions: PARAMETER_DESCRIPTIONS,
 };
-//# sourceMappingURL=get_native_livekit_core_integration_def.js.map

package/tools/definitions/get_usersig_def.js

@@ -24,4 +24,3 @@ export const GET_USERSIG_DEFINITION = {
         userID: '登录腾讯云应用的 userID',
     },
 };
-//# sourceMappingURL=get_usersig_def.js.map

package/tools/definitions/get_web_call_uikit_integration_def.js

@@ -1,3 +1,4 @@
+import { INTEGRATION_BOUNDARY_SUFFIX } from './integration-boundary.js';
 const TOOL_DESCRIPTION = `
 用途：
 返回 Web TUICallKit preset 集成文档，适合实现 PC/H5 音视频通话应用。
@@ -15,6 +16,7 @@ Web Call UIKit, Web TUICallKit, TUICallKit, preset 集成, React, Vue, PC, H5,
 边界：
 - 当用户未明确平台或框架时，应先调用 'present_framework_choice'
 - 面向 Web CallKit preset 整体集成，不负责 API 细节或交互式框架选择
+${INTEGRATION_BOUNDARY_SUFFIX}
 `;
 const PARAMETER_DESCRIPTIONS = {
     framework: '目标框架。参数名固定为 framework，禁止传 platform。可选值：react | vue。',
@@ -25,4 +27,3 @@ export const GET_WEB_CALL_UIKIT_INTEGRATION_DEFINITION = {
     description: TOOL_DESCRIPTION,
     parameter_descriptions: PARAMETER_DESCRIPTIONS,
 };
-//# sourceMappingURL=get_web_call_uikit_integration_def.js.map

package/tools/definitions/get_web_chat_uikit_integration_def.js

@@ -1,3 +1,4 @@
+import { INTEGRATION_BOUNDARY_SUFFIX } from './integration-boundary.js';
 const TOOL_DESCRIPTION = `
 用途：
 返回 Web Chat UIKit 集成文档，适合实现完整聊天应用或单聊天窗口接入。
@@ -16,6 +17,7 @@ Web Chat UIKit, TUIKit, IM, 聊天, 会话列表, 聊天窗口, React, Vue, full
 边界：
 - 当用户未明确平台或框架时，应先调用 'present_framework_choice'
 - 面向 Web Chat UIKit 整体集成，不负责组件级细节或交互式框架选择
+${INTEGRATION_BOUNDARY_SUFFIX}
 `;
 const PARAMETER_DESCRIPTIONS = {
     framework: '目标框架。参数名固定为 framework，禁止传 platform。可选值：react | vue。',
@@ -27,4 +29,3 @@ export const GET_WEB_CHAT_UIKIT_INTEGRATION_DEFINITION = {
     description: TOOL_DESCRIPTION,
     parameter_descriptions: PARAMETER_DESCRIPTIONS,
 };
-//# sourceMappingURL=get_web_chat_uikit_integration_def.js.map

package/tools/definitions/get_web_live_uikit_integration_def.js

@@ -1,9 +1,10 @@
+import { INTEGRATION_BOUNDARY_SUFFIX } from './integration-boundary.js';
 const TOOL_DESCRIPTION = `
 用途：
 返回 Web Live UIKit 页面级集成文档，适合接入直播列表页、观看页、开播页和连麦入口页。
 
 典型适用问题：
-Web Live UIKit, TUILiveUIKit, Vue, 页面级集成, 页面接入, 列表页, 观看页, 开播页, 连麦入口页, liveList, livePlayer-desk, livePlayer-h5, livePusher, CoGuestPanel
+Web Live UIKit, TUILiveUIKit, Vue, 页面级集成, 页面接入, 列表页, 观看页, 开播页, liveList, livePlayer-desk, livePlayer-h5, livePusher
 
 输入：
 - goals: 功能列表
@@ -14,9 +15,10 @@ Web Live UIKit, TUILiveUIKit, Vue, 页面级集成, 页面接入, 列表页, 观
 
 边界：
 - 当前主要面向 Web Vue 页面级接入，不负责 State API 字段方法或单组件详解
+${INTEGRATION_BOUNDARY_SUFFIX}
 `;
 const PARAMETER_DESCRIPTIONS = {
-    goals: '功能列表。可选值：liveList | livePlayer-desk | livePlayer-h5 | livePusher | CoGuestPanel。',
+    goals: '功能列表。可选值：liveList | livePlayer-desk | livePlayer-h5 | livePusher。',
     prompt: '用户的原始问题全文，保留完整上下文，不要压缩成关键词摘要。',
 };
 export const GET_WEB_LIVE_UIKIT_INTEGRATION_DEFINITION = {
@@ -24,4 +26,3 @@ export const GET_WEB_LIVE_UIKIT_INTEGRATION_DEFINITION = {
     description: TOOL_DESCRIPTION,
     parameter_descriptions: PARAMETER_DESCRIPTIONS,
 };
-//# sourceMappingURL=get_web_live_uikit_integration_def.js.map

package/tools/definitions/get_web_room_core_integration_def.js

@@ -0,0 +1,46 @@
+import { INTEGRATION_BOUNDARY_SUFFIX } from './integration-boundary.js';
+const TOOL_DESCRIPTION = `
+用途：
+返回 Web RoomKit Atomicx Core 基础集成文档，适合基于 Atomicx API 自实现会议室（无预制 UI），完成登录、房间状态与设备能力接入。
+
+典型适用问题（共用触发词，可能同时命中 'get_web_room_uikit_integration' preset 工具）：
+Web RoomKit, TUIRoomKit, Atomicx, Vue, 集成 RoomKit, 接入会议, 会议室, meeting, room
+命中以上共用触发词时，请**先主动追问用户**："您希望使用预制 UI 快速集成（TUIRoomUIKit preset），还是基于 Atomicx API 自实现会议室？" 用户选择"自实现/Atomicx/Core"后再调用本工具；选择"预制/preset/默认 UI"则调用 'get_web_room_uikit_integration'。
+
+典型适用问题（Core 专属触发词，仅命中本工具，无需追问，直接调用）：
+Atomicx API, 自实现会议室, 自定义会议 UI, 不用预制 UI, useRoomState, useDeviceState, useLoginState, room-state, device-state, device-detection
+
+输入：
+- framework: vue
+- goals: room-state | device-detection | device-state
+- prompt: 用户的原始问题全文，保留完整上下文，不要压缩成关键词摘要
+
+返回：
+- content: [{ type: 'text', text: 文档正文或说明文本 }]
+
+边界：
+- 当用户未明确平台或框架时，应先调用 'present_framework_choice'
+- 面向 Atomicx Core 基础接入（登录 + room-state / device 模块），不负责预制 UI 页面模板
+- 屏幕分享、虚拟背景、预约会议等扩展模块 → 调用 \`search_trtc_knowledge(types=[feature])\`
+- **登录约束**：必须调用 \`get_usersig\` 获取 UserSig，再使用 \`useLoginState.login\` 登录；**禁止**在项目内实现 UserSig 生成（如 GenerateTestUserSig）
+${INTEGRATION_BOUNDARY_SUFFIX}
+`;
+const PARAMETER_DESCRIPTIONS = {
+    framework: '目标框架。参数名固定为 framework，禁止传 platform。固定值：vue。',
+    goals: '功能列表。可选值：room-state（房间状态）| device-detection（设备检测）| device-state（设备状态）。',
+    prompt: '用户的原始问题全文，保留完整上下文，不要压缩成关键词摘要。',
+};
+const ANTI_HALLUCINATION_HEADER = `本文档基于 Atomicx Core API 自实现方案，严禁照搬 TUIRoomUIKit 预制 UI 组件。\n\n`;
+const ANTI_HALLUCINATION_CONSTRAINT = `
+---
+【AI 代码生成约束 - Atomicx Core 方案】
+请严格基于文档内容生成代码。登录流程 MUST 调用 get_usersig 工具获取 UserSig，再使用 useLoginState.login；禁止在项目中实现 GenerateTestUserSig 或本地 UserSig 签发逻辑。
+---
+`;
+export const GET_WEB_ROOM_CORE_INTEGRATION_DEFINITION = {
+    name: 'get_web_room_core_integration',
+    description: TOOL_DESCRIPTION,
+    parameter_descriptions: PARAMETER_DESCRIPTIONS,
+    anti_hallucination_header: ANTI_HALLUCINATION_HEADER,
+    anti_hallucination_constraint: ANTI_HALLUCINATION_CONSTRAINT,
+};

package/tools/definitions/get_web_room_uikit_integration_def.js

@@ -1,3 +1,4 @@
+import { INTEGRATION_BOUNDARY_SUFFIX } from './integration-boundary.js';
 const TOOL_DESCRIPTION = `
 用途：
 返回 Web Room UIKit 预制 UI 集成文档，适合接入会议入口页、会议室页面和默认会议应用方案。
@@ -14,6 +15,8 @@ Web Room UIKit, TUIRoomUIKit, Atomicx, Vue, 预制 UI, 默认会议方案, meeti
 
 边界：
 - 面向预制 UI 主接入，不负责 Atomicx API 或单功能模块的自定义实现细节
+- 用户要自实现 Atomicx 会议室 → 调用 'get_web_room_core_integration'
+${INTEGRATION_BOUNDARY_SUFFIX}
 `;
 const PARAMETER_DESCRIPTIONS = {
     framework: '目标框架。参数名固定为 framework，禁止传 platform。固定值：vue。',
@@ -24,4 +27,3 @@ export const GET_WEB_ROOM_UIKIT_INTEGRATION_DEFINITION = {
     description: TOOL_DESCRIPTION,
     parameter_descriptions: PARAMETER_DESCRIPTIONS,
 };
-//# sourceMappingURL=get_web_room_uikit_integration_def.js.map

package/tools/definitions/integration-boundary.js

@@ -0,0 +1,5 @@
+/** Phase 1 统一追加到 9× integration 工具「边界」段末尾 */
+export const INTEGRATION_BOUNDARY_SUFFIX = `
+- **Codegen 专用**：仅当用户明确要求「集成进项目 / 写接入代码 / 帮我实现接入 / 生成工程代码」时调用本工具
+- **纯咨询或查阅**（怎么用、是什么、有哪些步骤、先看文档、错误排查、API/组件说明）→ 调用 \`search_trtc_knowledge\`，**不要**调用本工具
+- 本工具属 codegen 链路：作答后**不**调用 \`record_answer\` / \`record_feedback\`（这两个仅属 \`search_trtc_knowledge\` 链路）`;