@tencent-rtc/mcp 1.4.7 → 1.6.0

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

@@ -2,29 +2,33 @@ import { z } from 'zod';
 import { PRESENT_FRAMEWORK_CHOICE_DEFINITION } from '../definitions/present_framework_choice_def.js';
 const PRODUCT_OPTIONS_MAP = {
     chat: {
-        title: 'Chat 聊天支持的平台或框架',
+        title: 'Supported Chat / IM platforms or frameworks',
         options: ['react', 'vue', 'flutter', 'android', 'ios'],
     },
     call: {
-        title: 'Call 音视频通话支持的平台或框架',
+        title: 'Supported Call / CallKit platforms or frameworks',
         options: ['react', 'vue', 'flutter', 'android', 'ios', 'uni-app'],
     },
     live: {
-        title: 'Live 直播互动支持的平台或框架',
-        options: ['vue', 'flutter', 'android', 'ios', 'uni-app'],
+        title: 'Supported Live / LiveKit platforms or frameworks',
+        options: ['vue', 'flutter', 'android', 'ios'],
     },
     room: {
-        title: 'Room 视频会议支持的平台或框架',
+        title: 'Supported Room / RoomKit platforms or frameworks',
         options: ['vue'],
     },
     rtcengine: {
-        title: 'WebRTC / rtcEngine 支持的平台或框架',
+        title: 'Supported Web TRTC / rtcEngine platforms or frameworks',
         options: ['web'],
     },
     native_trtc_sdk: {
-        title: 'Native TRTC SDK 支持的平台或框架',
+        title: 'Supported Native TRTC SDK platforms or frameworks',
         options: ['android', 'ios', 'c++'],
     },
+    push: {
+        title: 'Supported Push / TIMPush platforms or frameworks',
+        options: ['android', 'ios', 'flutter', 'harmonyos', 'react-native', 'uni-app', 'unity', 'unreal-engine', 'donut'],
+    },
 };
 function buildSelectionText(product, selectionText) {
     const config = PRODUCT_OPTIONS_MAP[product];
@@ -34,19 +38,21 @@ function buildSelectionText(product, selectionText) {
     const options = config.options.map((option) => `- '${option}'`).join('\n');
     return `${selectionText}
 
-请先让用户选择以下平台或框架：
+Please ask the user to choose one of the supported platforms or frameworks:
 
-${config.title}：
+${config.title}:
 ${options}
 
-请等待用户回复具体平台后，再调用对应的集成工具或查询工具。`;
+After the user replies (hard rule — do not skip):
+- **Consultation / docs / API / component / feature lookup** → MUST call \`search_trtc_knowledge\` with **product + framework**
+- **Write integration code into a project** → MUST call the matching \`get_*_integration\` tool`;
 }
 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 {
@@ -54,10 +60,9 @@ const registryPresentFrameworkChoiceTool = (mcpServer) => {
                 {
                     type: 'text',
                     text: buildSelectionText(product, selectionText),
-                }
-            ]
+                },
+            ],
         };
     });
 };
 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.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().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 ? params.product.join(',') : '',
+            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().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().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 = `
 Purpose:
 Return Native TUICallKit preset integration docs for setting up a complete mobile calling experience with a ready-made call UI.
@@ -20,7 +21,8 @@ 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.
-- Use this tool for the main Native CallKit preset integration path. It is not for feature-level settings such as ringtone, floating window, avatar, profile info, or virtual background.
+- 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}
 `;
 const PARAMETER_DESCRIPTIONS = {
     framework: 'Target platform. The parameter name must be framework. Do not use platform. Allowed values: 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 = `
 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.
@@ -15,14 +16,15 @@ Input:
 - 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 }]. The \`text\` field is assembled as: a short AtomicXCore-only preamble, then the retrieved markdown instructions, then a closing constraint block. Together they instruct the model not to use undocumented APIs or UI-kit entry points (e.g. TUILogin, TUICallKit) when generating code from these docs.
+- content: [{ type: 'text', text: documentation content 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 to 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 single-feature APIs such as beauty, virtual background, floating window, or picture-in-picture.
+- 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.
+${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.',
@@ -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 = `
 Purpose:
 Return Native Chat UIKit integration docs for building either a full IM app or a single chat window on mobile.
@@ -15,10 +16,12 @@ Returns:
 
 Boundaries:
 - If the user has not specified a platform or framework, call 'present_framework_choice' first.
-- This tool is for full Native Chat UIKit integration. It is not for platform selection or deep single-feature lookup.
+- This tool is for full Native Chat UIKit integration (Compose / SwiftUI codegen path). It is not for platform selection or deep single-feature lookup.
+- Android View / iOS UIKit integration lookup -> use search_trtc_knowledge instead.
+${INTEGRATION_BOUNDARY_SUFFIX}
 `;
 const PARAMETER_DESCRIPTIONS = {
-    framework: 'Target platform. The parameter name must be framework. Do not use platform. Allowed values: flutter | android | ios.',
+    framework: 'Target platform. The parameter name must be framework. Do not use platform. Allowed values: flutter | android | ios. android/ios are the Compose / SwiftUI codegen path; for View/UIKit integration lookup use search_trtc_knowledge.',
     goals: 'Goal array. Exactly one value is allowed: full-featured (full app) | chat-only (single chat window).',
     prompt: "The user's original question in full. Keep the full context. Do not compress it into keywords or a short summary.",
 };
@@ -27,4 +30,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 = `
 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.
@@ -16,14 +17,14 @@ Returns:
 
 Boundaries:
 - If the user has not specified a platform or framework, call 'present_framework_choice' first.
-- Use this tool for the main AtomicXCore-based setup path for live streaming or voice rooms.
-- It is not for co-guest, PK, member list, beauty, audio effects, barrage, or gifts.
-- It returns core/store-level integration docs, not a full preset UIKit page template.
+- This tool is for AtomicXCore-based live streaming or voice room base integration. It is not for co-guest, PK, member list, beauty, audio effects, barrage, or gifts.
+- It returns Core/Store-level integration docs, not a full preset UIKit page template.
+${INTEGRATION_BOUNDARY_SUFFIX}
 `;
 const PARAMETER_DESCRIPTIONS = {
-    scenario: 'Scenario type. Allowed values: live | voice. Use integration for publishing, viewing, or room list. Use features for co-guest, PK, member list, beauty, audio effects, barrage, or gifts.',
+    scenario: 'Scenario type. Allowed values: live | voice. Use integration for publishing, viewing, or room list. Use search_trtc_knowledge for co-guest, PK, member list, beauty, audio effects, barrage, or gifts.',
     framework: 'Target platform. The parameter name must be framework. Do not use platform. Allowed values: android | ios | flutter | uni-app.',
-    goals: 'Feature list. Allowed values: host_streaming | audience_streaming | live_list.',
+    goals: 'Feature list. Allowed values: host_streaming (host publish) | audience_streaming (audience watch) | live_list (room list).',
     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_LIVEKIT_CORE_INTEGRATION_DEFINITION = {
@@ -31,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: 'The userID used to log in to the Tencent Cloud application.',
     },
 };
-//# sourceMappingURL=get_usersig_def.js.map

package/tools/definitions/get_web_call_uikit_integration_def.js

@@ -1,9 +1,10 @@
+import { INTEGRATION_BOUNDARY_SUFFIX } from './integration-boundary.js';
 const TOOL_DESCRIPTION = `
 Purpose:
 Return Web TUICallKit preset integration docs for setting up a complete calling experience on PC or H5.
 
 Typical use cases:
-Web Call UIKit, Web TUICallKit, TUICallKit, preset integration, React, Vue, PC, H5, audio/video calling, video call, voice call, set up CallKit, wire CallKit into my project, calling flow, answering flow
+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:
 - framework: react | vue
@@ -14,7 +15,8 @@ Returns:
 
 Boundaries:
 - If the user has not specified a platform or framework, call 'present_framework_choice' first.
-- Use this tool for the main Web CallKit preset integration path. It is not for API details or feature-level settings.
+- This tool is for Web CallKit preset integration. It is not for API details or interactive framework selection.
+${INTEGRATION_BOUNDARY_SUFFIX}
 `;
 const PARAMETER_DESCRIPTIONS = {
     framework: 'Target framework. The parameter name must be framework. Do not use platform. Allowed values: 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 = `
 Purpose:
 Return Web Chat UIKit integration docs for building either a full chat app or a single chat window.
@@ -16,6 +17,7 @@ Returns:
 Boundaries:
 - If the user has not specified a platform or framework, call 'present_framework_choice' first.
 - This tool is for full Web Chat UIKit integration. It is not for component-level details or interactive framework selection.
+${INTEGRATION_BOUNDARY_SUFFIX}
 `;
 const PARAMETER_DESCRIPTIONS = {
     framework: 'Target framework. The parameter name must be framework. Do not use platform. Allowed values: 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 = `
 Purpose:
 Return Web Live UIKit page-level integration docs for wiring live list, player, publish, and co-guest entry pages.
 
 Typical use cases:
-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, co-guest entry page, liveList, livePlayer-desk, livePlayer-h5, livePusher, CoGuestPanel
+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:
 - goals: feature list
@@ -13,12 +14,11 @@ Returns:
 - content: [{ type: 'text', text: documentation content or explanatory text }]
 
 Boundaries:
-- Use this tool for Web Vue page-level integration.
-- It is not for State API field, store field, or method lookup.
-- It is not for single-component usage details.
+- This tool is primarily for Web Vue page-level integration. It is not for State API fields/methods or single-component deep dives.
+${INTEGRATION_BOUNDARY_SUFFIX}
 `;
 const PARAMETER_DESCRIPTIONS = {
-    goals: 'Feature list. Allowed values: liveList | livePlayer-desk | livePlayer-h5 | livePusher | CoGuestPanel.',
+    goals: 'Feature list. Allowed values: liveList | livePlayer-desk | livePlayer-h5 | livePusher.',
     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_WEB_LIVE_UIKIT_INTEGRATION_DEFINITION = {
@@ -26,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,49 @@
+import { INTEGRATION_BOUNDARY_SUFFIX } from './integration-boundary.js';
+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\`):
+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\`.
+
+Core-only trigger phrases (call directly, no follow-up needed):
+Atomicx API, custom meeting room, custom room UI, without preset UI, useRoomState, useDeviceState, useLoginState, room-state, device-state, device-detection
+
+Input:
+- 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 }]
+
+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.
+${INTEGRATION_BOUNDARY_SUFFIX}
+`;
+const PARAMETER_DESCRIPTIONS = {
+    framework: 'Target framework. The parameter name must be framework. Do not use platform. Fixed value: vue.',
+    goals: 'Goal array. Allowed values: 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.",
+};
+const ANTI_HALLUCINATION_HEADER = 'This document is for the Atomicx Core custom implementation path. Do not copy preset TUIRoomUIKit UI components as if they were Core APIs.\\n\\n';
+const ANTI_HALLUCINATION_CONSTRAINT = `
+---
+[AI code generation constraints - Atomicx Core path]
+Generate code strictly from the documentation. The login flow MUST call the get_usersig tool to obtain a UserSig, then call useLoginState.login. Never implement GenerateTestUserSig or any local UserSig issuing logic in the project.
+---
+`;
+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,9 +1,10 @@
+import { INTEGRATION_BOUNDARY_SUFFIX } from './integration-boundary.js';
 const TOOL_DESCRIPTION = `
 Purpose:
 Return Web Room UIKit preset integration docs for the main meeting entry page, room page, and default meeting app flow.
 
 Typical use cases:
-Web Room UIKit, TUIRoomUIKit, Atomicx, Vue, preset UI, default meeting app, meeting app, home.vue, room.vue, meeting entry page, meeting room page, H5 meeting, PC meeting, set up Room UIKit, integrate meeting UI, wire the preset meeting flow
+Web Room UIKit, TUIRoomUIKit, Atomicx, Vue, preset UI, default meeting app, meeting app, home.vue, room.vue, meeting entry page, meeting room page, H5 meeting, PC meeting, integrate Room UIKit
 
 Input:
 - framework: vue
@@ -13,9 +14,9 @@ Returns:
 - content: [{ type: 'text', text: documentation content or explanatory text }]
 
 Boundaries:
-- Use this tool for the preset meeting UI integration path.
-- It is not for Atomicx API details.
-- It is not for custom single-feature implementations or hook-level queries.
+- This tool is for preset UI integration. It is not for Atomicx API details or custom single-feature modules.
+- For custom Atomicx room implementation -> call 'get_web_room_core_integration'.
+${INTEGRATION_BOUNDARY_SUFFIX}
 `;
 const PARAMETER_DESCRIPTIONS = {
     framework: 'Target framework. The parameter name must be framework. Do not use platform. Fixed value: vue.',
@@ -26,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 @@
+/** Shared boundary text appended to integration tool descriptions. */
+export const INTEGRATION_BOUNDARY_SUFFIX = `
+- **Codegen only**: Call this tool only when the user explicitly wants integration code added into a project, wants you to implement the integration, or wants generated starter code.
+- **Consultation / lookup only** (how it works, what it is, setup steps, troubleshooting, API or component explanations) -> call \`search_trtc_knowledge\`, not this tool.
+- This tool belongs to the codegen flow: after answering, do **not** call \`record_answer\` or \`record_feedback\` (those belong only to the \`search_trtc_knowledge\` flow).`;