@tencent-rtc/mcp 1.3.8 → 1.4.0

package/tools/common/present_framework_choice.js

@@ -0,0 +1,63 @@
+import { z } from 'zod';
+import { PRESENT_FRAMEWORK_CHOICE_DEFINITION } from '../definitions/present_framework_choice_def.js';
+const PRODUCT_OPTIONS_MAP = {
+    chat: {
+        title: 'Chat 聊天支持的平台或框架',
+        options: ['react', 'vue', 'flutter', 'android', 'ios'],
+    },
+    call: {
+        title: 'Call 音视频通话支持的平台或框架',
+        options: ['react', 'vue', 'flutter', 'android', 'ios'],
+    },
+    live: {
+        title: 'Live 直播互动支持的平台或框架',
+        options: ['vue', 'flutter', 'android', 'ios', 'uni-app'],
+    },
+    room: {
+        title: 'Room 视频会议支持的平台或框架',
+        options: ['vue'],
+    },
+    rtcengine: {
+        title: 'WebRTC / rtcEngine 支持的平台或框架',
+        options: ['web'],
+    },
+    native_trtc_sdk: {
+        title: 'Native TRTC SDK 支持的平台或框架',
+        options: ['android', 'ios', 'c++'],
+    },
+};
+function buildSelectionText(product, selectionText) {
+    const config = PRODUCT_OPTIONS_MAP[product];
+    if (!config) {
+        return selectionText;
+    }
+    const options = config.options.map((option) => `- '${option}'`).join('\n');
+    return `${selectionText}
+
+请先让用户选择以下平台或框架：
+
+${config.title}：
+${options}
+
+请等待用户回复具体平台后，再调用对应的集成工具或查询工具。`;
+}
+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 }) => {
+        return {
+            content: [
+                {
+                    type: 'text',
+                    text: buildSelectionText(product, selectionText),
+                }
+            ]
+        };
+    });
+};
+export { registryPresentFrameworkChoiceTool };
+//# sourceMappingURL=present_framework_choice.js.map

package/tools/common/present_framework_choice.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"present_framework_choice.js","sourceRoot":"","sources":["../../../src/tools/common/present_framework_choice.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AACxB,OAAO,EAAE,mCAAmC,EAAE,MAAM,gDAAgD,CAAC;AAErG,MAAM,mBAAmB,GAAyD;IAChF,IAAI,EAAE;QACJ,KAAK,EAAE,iBAAiB;QACxB,OAAO,EAAE,CAAC,OAAO,EAAE,KAAK,EAAE,SAAS,EAAE,SAAS,EAAE,KAAK,CAAC;KACvD;IACD,IAAI,EAAE;QACJ,KAAK,EAAE,oBAAoB;QAC3B,OAAO,EAAE,CAAC,OAAO,EAAE,KAAK,EAAE,SAAS,EAAE,SAAS,EAAE,KAAK,CAAC;KACvD;IACD,IAAI,EAAE;QACJ,KAAK,EAAE,mBAAmB;QAC1B,OAAO,EAAE,CAAC,KAAK,EAAE,SAAS,EAAE,SAAS,EAAE,KAAK,EAAE,SAAS,CAAC;KACzD;IACD,IAAI,EAAE;QACJ,KAAK,EAAE,mBAAmB;QAC1B,OAAO,EAAE,CAAC,KAAK,CAAC;KACjB;IACD,SAAS,EAAE;QACT,KAAK,EAAE,6BAA6B;QACpC,OAAO,EAAE,CAAC,KAAK,CAAC;KACjB;IACD,eAAe,EAAE;QACf,KAAK,EAAE,0BAA0B;QACjC,OAAO,EAAE,CAAC,SAAS,EAAE,KAAK,EAAE,KAAK,CAAC;KACnC;CACF,CAAC;AAEF,SAAS,kBAAkB,CAAC,OAAe,EAAE,aAAqB;IAChE,MAAM,MAAM,GAAG,mBAAmB,CAAC,OAAO,CAAC,CAAC;IAE5C,IAAI,CAAC,MAAM,EAAE,CAAC;QACZ,OAAO,aAAa,CAAC;IACvB,CAAC;IAED,MAAM,OAAO,GAAG,MAAM,CAAC,OAAO,CAAC,GAAG,CAAC,CAAC,MAAM,EAAE,EAAE,CAAC,MAAM,MAAM,GAAG,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;IAE3E,OAAO,GAAG,aAAa;;;;EAIvB,MAAM,CAAC,KAAK;EACZ,OAAO;;8BAEqB,CAAC;AAC/B,CAAC;AAED,MAAM,kCAAkC,GAAG,CAAC,SAAoB,EAAE,EAAE;IAClE,MAAM,EAAE,IAAI,EAAE,WAAW,EAAE,aAAa,EAAE,sBAAsB,EAAE,GAAG,mCAAmC,CAAC;IACzG,SAAS,CAAC,YAAY,CACpB,IAAI,EACJ;QACC,WAAW;QACV,WAAW,EAAE;YACX,OAAO,EAAE,CAAC,CAAC,IAAI,CAAC,CAAC,MAAM,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM,EAAE,WAAW,EAAE,iBAAiB,CAAC,CAAC,CAAC,QAAQ,CAAC,sBAAsB,CAAC,OAAO,CAAC;SAC3H;KACF,EACD,CAAC,EAAE,OAAO,EAAE,EAAE,EAAE;QACd,OAAO;YACL,OAAO,EAAE;gBACP;oBACE,IAAI,EAAE,MAAM;oBACZ,IAAI,EAAE,kBAAkB,CAAC,OAAO,EAAE,aAAa,CAAC;iBACjD;aACF;SACF,CAAC;IACJ,CAAC,CAAC,CAAC;AACP,CAAC,CAAC;AAEF,OAAO,EAAE,kCAAkC,EAAE,CAAC"}

package/tools/definitions/get_callkit_api_def.js

@@ -0,0 +1,29 @@
+const TOOL_DESCRIPTION = `
+Purpose:
+Return cross-platform CallKit preset API docs for feature-level questions after the platform is already known.
+
+Typical use cases:
+CallKit API, TUICallKit API, React, Vue, Android, iOS, Flutter, what API should I call, which method starts a call, what is the latest API for this, how do I configure this feature, how do I set this up, how do I pass parameters, which callback should I listen to, custom UI, method usage, event callbacks, calls, join, setSelfInfo
+
+Input:
+- framework: react | vue | android | ios | flutter
+- 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.
+- Use this tool for platform-specific CallKit API, method, callback, and configuration lookup.
+- Do not use it for the main integration guide or for interactive platform selection.
+`;
+const PARAMETER_DESCRIPTIONS = {
+    framework: 'Target platform or framework. The parameter name must be framework. Allowed values: react | vue | android | ios | flutter.',
+    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_CALLKIT_API_DEFINITION = {
+    name: 'get_callkit_api',
+    description: TOOL_DESCRIPTION,
+    parameter_descriptions: PARAMETER_DESCRIPTIONS,
+};
+//# sourceMappingURL=get_callkit_api_def.js.map

package/tools/definitions/get_callkit_api_def.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"get_callkit_api_def.js","sourceRoot":"","sources":["../../../src/tools/definitions/get_callkit_api_def.ts"],"names":[],"mappings":"AAAA,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;CAkBxB,CAAC;AAEF,MAAM,sBAAsB,GAAG;IAC7B,SAAS,EAAE,4HAA4H;IACvI,MAAM,EAAE,mHAAmH;CAC5H,CAAC;AAEF,MAAM,CAAC,MAAM,0BAA0B,GAAG;IACxC,IAAI,EAAE,iBAAiB;IACvB,WAAW,EAAE,gBAAgB;IAC7B,sBAAsB,EAAE,sBAAsB;CAC/C,CAAC"}

package/tools/definitions/get_faq_def.js

@@ -1,28 +1,27 @@
 const TOOL_DESCRIPTION = `
-[CORE FUNCTION]: This is a unified knowledge retrieval tool (FAQ/Documentation Query) designed to fetch relevant Markdown document content from multi-product knowledge bases based on the user's query and specified parameters.\n
+Purpose:
+Return Tencent RTC FAQ results for common questions, known issues, error diagnosis, authentication guidance, console configuration, and troubleshooting.
 
-[SCOPE]: This tool addresses common questions and integration guides for three main application types:\n
-1. Chat Applications (Chat): Covers solutions for mobile (Native) and Web (React/Vue) platforms.\n
-2. Audio/Video Call Applications (Call): Covers solutions for mobile (Native) and Web (React/Vue) platforms.\n
-3. Real-Time Communication (TRTC): Includes FAQs for RTC/WebRTC platforms, guides on deploying user authentication services, and details on the UserSig generation algorithm.\n
+Typical use cases:
+FAQ, common questions, known issue, troubleshooting, auth failure, how to generate userSig, userSig principles, userSig issuing flow, server-side auth, console configuration, billing, chat faq, call faq, live faq, room faq, rtcengine faq, native trtc sdk faq, react faq, vue faq, web faq, android faq, ios faq, flutter faq, c++ faq
 
-[RETRIEVAL CAPABILITIES]: The tool supports precise filtering and retrieval using the following key parameters:\n
-- query: The text of the user's input query or question.\n
-- product: The product name inferred by the LLM for routing (e.g., chat, call, live, room, rtcengine).\n
-- framework: The platform or framework inferred by the LLM for routing (e.g., react, vue, web, flutter, android, ios).\n
+Input:
+- prompt: The user's original question in full. Keep the full context. Do not compress it into keywords or a short summary.
+- product: chat | call | live | room | rtcengine | native_trtc_sdk
+- framework: react | vue | web | flutter | android | ios | c++
 
-[KEYWORDS]: FAQ, Knowledge Base, Document Retrieval, Common Questions, Chat, Call, TRTC, Real-Time Communication, User Authentication, UserSig, SDK.\n
+Returns:
+- content: [{ type: 'text', text: documentation content or explanatory text }]
 
-[Mandatory Constraints]: \n
- 1. Product Selection Constraint: If the LLM cannot explicitly infer the target product line (product) from the user's prompt, it must prioritize guiding the user to select one of the following products: (chat, call, live, room, rtcengine).
- 2. Framework Selection Constraint: If the LLM cannot explicitly infer the target platform or framework (framework) from the user's prompt, it must prioritize calling the 'present_framework_choice' tool to guide the user to select the platform/framework.
-
-[RETURN FORMAT]: Returns raw Markdown content and a structured JSON object.
+Boundaries:
+- Use this tool for FAQ, error codes, console issues, authentication guidance, and troubleshooting.
+- It does not return the main integration guide.
+- It does not return dedicated component or API topic docs.
 `;
 const PARAMETER_DESCRIPTIONS = {
-    query: 'The text of the user\'s input query or question.',
-    product: 'The target product name inferred by the LLM (e.g., chat, call, live, room, rtcengine).',
-    framework: 'The target platform or framework name inferred by the LLM (e.g., react, vue, web, 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.",
+    product: 'Target product. Allowed values: chat | call | live | room | rtcengine | native_trtc_sdk.',
+    framework: 'Target platform or framework. The parameter name must be framework. Allowed values: react | vue | web | flutter | android | ios | c++.',
 };
 export const GET_FAQ_DEFINITION = {
     name: 'get_faq',

package/tools/definitions/get_faq_def.js.map

@@ -1 +1 @@
-{"version":3,"file":"get_faq_def.js","sourceRoot":"","sources":["../../../src/tools/definitions/get_faq_def.ts"],"names":[],"mappings":"AAAA,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;;;CAoBxB,CAAC;AAEF,MAAM,sBAAsB,GAAG;IAC7B,KAAK,EAAE,kDAAkD;IACzD,OAAO,EAAE,wFAAwF;IACjG,SAAS,EAAE,2GAA2G;CACvH,CAAC;AAEF,MAAM,CAAC,MAAM,kBAAkB,GAAG;IAChC,IAAI,EAAE,SAAS;IACf,WAAW,EAAE,gBAAgB;IAC7B,sBAAsB,EAAE,sBAAsB;CAC/C,CAAC"}
+{"version":3,"file":"get_faq_def.js","sourceRoot":"","sources":["../../../src/tools/definitions/get_faq_def.ts"],"names":[],"mappings":"AAAA,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;;CAmBxB,CAAC;AAEF,MAAM,sBAAsB,GAAG;IAC7B,MAAM,EAAE,mHAAmH;IAC3H,OAAO,EAAE,0FAA0F;IACnG,SAAS,EAAE,wIAAwI;CACpJ,CAAC;AAEF,MAAM,CAAC,MAAM,kBAAkB,GAAG;IAChC,IAAI,EAAE,SAAS;IACf,WAAW,EAAE,gBAAgB;IAC7B,sBAAsB,EAAE,sBAAsB;CAC/C,CAAC"}

package/tools/definitions/get_native_call_uikit_integration_def.js

@@ -1,29 +1,26 @@
 const TOOL_DESCRIPTION = `
-【Core Purpose】: As a professional Native audio/video call TUICallKit integration assistant, this tool is specifically designed to provide Agents with workflow action instructions and real-time aggregated latest documentation content to guide LLM in helping users implement mobile audio/video call features.
+Purpose:
+Return Native TUICallKit preset integration docs for setting up a complete mobile calling experience.
 
-【Functional Goals】:
-Integrate complete audio/video call features. Including one-on-one calls, group calls, call answering, call interface, etc. **Suitable for building WeChat/WeCom-style audio/video call applications, supporting one-on-one and group call scenarios.**
+Typical use cases:
+Native Call UIKit, Native TUICallKit, TUICallKit, preset integration, audio/video calling, video call, voice call, Flutter, Android, iOS, set up CallKit, wire CallKit into my app, one-to-one call, group call, calling flow, answering flow
 
-【Keywords】:
-'Native', 'Mobile', 'Call', 'TUICallKit', 'Audio/Video Call', 'Video Call', 'Voice Call', 'WeChat', 'WeCom', 'Flutter', 'Android', 'iOS', 'Integration', 'One-on-One Call', 'Group Call', 'Call', 'Answer'.
+Input:
+- 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.
 
-【Action Instructions and Workflow Guidance】:
-When handling user requirements, Agents should use the llm_code_generation_instructions_md field returned by this tool. This field contains:
-1. Core workflow instructions: Including environment preparation, dependency installation, SDK initialization, UserSig authentication, and component version information.
-2. Real-time documentation content: Providing the latest content from official integration guides.
+Returns:
+- content: [{ type: 'text', text: documentation content or explanatory text }]
 
-LLM must prioritize and exclusively use the real-time content returned by this tool to generate code, avoiding accessing external URLs independently.
-
-【Mandatory Constraints】:
-1. Platform Selection Constraint: If the user has not explicitly specified a platform, or the intent is unclear, must first call the 'present_framework_choice' tool to guide the user to choose among flutter, android, ios.
-2. Result Recording Constraint: After TUICallKit component integration is complete and the project starts successfully, must call the 'record_result' tool to record integration results.
-
-【Supported Platforms】: flutter, android, ios.
+Boundaries:
+- If the user has not specified a platform or framework, call 'present_framework_choice' first.
+- 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.
 `;
 const PARAMETER_DESCRIPTIONS = {
-    framework: 'Native audio/video call TUICallKit platform type. Available values: flutter (Flutter cross-platform), android (Android native), ios (iOS native).',
+    framework: 'Target platform. The parameter name must be framework. Do not use platform. Allowed values: 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.",
 };
-export const GET_NATIVE_CALL_UIKIT_DEFINITION = {
+export const GET_NATIVE_CALL_UIKIT_INTEGRATION_DEFINITION = {
     name: 'get_native_call_uikit_integration',
     description: TOOL_DESCRIPTION,
     parameter_descriptions: PARAMETER_DESCRIPTIONS,

package/tools/definitions/get_native_call_uikit_integration_def.js.map

@@ -1 +1 @@
-{"version":3,"file":"get_native_call_uikit_integration_def.js","sourceRoot":"","sources":["../../../src/tools/definitions/get_native_call_uikit_integration_def.ts"],"names":[],"mappings":"AAAA,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;;;;CAqBxB,CAAC;AAEF,MAAM,sBAAsB,GAAG;IAC7B,SAAS,EAAE,mJAAmJ;CAC/J,CAAC;AAEF,MAAM,CAAC,MAAM,gCAAgC,GAAG;IAC9C,IAAI,EAAE,mCAAmC;IACzC,WAAW,EAAE,gBAAgB;IAC7B,sBAAsB,EAAE,sBAAsB;CAC/C,CAAC"}
+{"version":3,"file":"get_native_call_uikit_integration_def.js","sourceRoot":"","sources":["../../../src/tools/definitions/get_native_call_uikit_integration_def.ts"],"names":[],"mappings":"AAAA,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;CAiBxB,CAAC;AAEF,MAAM,sBAAsB,GAAG;IAC7B,SAAS,EAAE,sHAAsH;IACjI,MAAM,EAAE,mHAAmH;CAC5H,CAAC;AAEF,MAAM,CAAC,MAAM,4CAA4C,GAAG;IAC1D,IAAI,EAAE,mCAAmC;IACzC,WAAW,EAAE,gBAAgB;IAC7B,sBAAsB,EAAE,sBAAsB;CAC/C,CAAC"}

package/tools/definitions/get_native_chat_uikit_feature_detail_def.js

@@ -0,0 +1,31 @@
+const TOOL_DESCRIPTION = `
+Purpose:
+Return Native Chat UIKit feature-detail docs for a single feature, including APIs, usage notes, and example code.
+
+Typical use cases:
+Native Chat UIKit, feature detail, Android, iOS, Flutter, theme, theme customization, dark mode, UI customization, TUITheme
+
+Input:
+- framework: android | ios | flutter
+- featureName: theme
+- 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 tool is for one chat feature or one focused topic. It is not for the main Chat UIKit integration path.
+- featureName must use a supported feature value.
+`;
+const PARAMETER_DESCRIPTIONS = {
+    framework: 'Target platform. The parameter name must be framework. Do not use platform. Allowed values: android | ios | flutter.',
+    featureName: 'Feature name. Currently supported: theme (theme customization).',
+    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_CHAT_UIKIT_FEATURE_DETAIL_DEFINITION = {
+    name: 'get_native_chat_uikit_feature_detail',
+    description: TOOL_DESCRIPTION,
+    parameter_descriptions: PARAMETER_DESCRIPTIONS,
+};
+//# sourceMappingURL=get_native_chat_uikit_feature_detail_def.js.map

package/tools/definitions/get_native_chat_uikit_feature_detail_def.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"get_native_chat_uikit_feature_detail_def.js","sourceRoot":"","sources":["../../../src/tools/definitions/get_native_chat_uikit_feature_detail_def.ts"],"names":[],"mappings":"AAAA,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;;CAmBxB,CAAC;AAEF,MAAM,sBAAsB,GAAG;IAC7B,SAAS,EAAE,sHAAsH;IACjI,WAAW,EAAE,iEAAiE;IAC9E,MAAM,EAAE,mHAAmH;CAC5H,CAAC;AAEF,MAAM,CAAC,MAAM,+CAA+C,GAAG;IAC7D,IAAI,EAAE,sCAAsC;IAC5C,WAAW,EAAE,gBAAgB;IAC7B,sBAAsB,EAAE,sBAAsB;CAC/C,CAAC"}

package/tools/definitions/get_native_chat_uikit_integration_def.js

@@ -1,29 +1,26 @@
 const TOOL_DESCRIPTION = `
-【Core Purpose】: As a professional Native chat TUIKit integration assistant, this tool is specifically designed to provide Agents with workflow action instructions and real-time aggregated latest documentation content to guide LLM in helping users implement mobile instant messaging (IM) features.
+Purpose:
+Return Native Chat UIKit integration docs for building either a full IM app or a single chat window on mobile.
 
-【Feature Goals】:
-1. full-featured: Integrate full functionality. Includes conversation list, chat window, group management, personal center, etc. **Suitable for building complete mobile applications in WeChat/Enterprise WeChat style, or as a core Tab module of an App.**
-2. chat-only: Integrate chat window only. **Suitable for lightweight conversation scenarios such as customer service consultation, online medical consultation, private chat on order details page, etc.**
+Typical use cases:
+Native Chat UIKit, TUIKit, IM, chat, conversation list, chat window, Flutter, Android, iOS, full-featured, chat-only, customer service chat, consultation chat
 
-【Keywords】:
-'Native', 'mobile', 'Chat', 'TUIKit', 'chat', 'instant messaging', 'WeChat', 'Enterprise WeChat', 'Flutter', 'Android', 'iOS', 'integration', 'customer service', 'medical consultation', 'TabBar', 'message entry', 'conversation list', 'dialog box'.
+Input:
+- 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.
 
-【Action Instructions and Workflow Guidance】:
-When processing user requirements, the Agent should use the llm_code_generation_instructions_md field returned by this tool. This field contains:
-1. Core workflow instructions: including environment preparation, dependency installation, SDK initialization, UserSig authentication, and component version descriptions.
-2. Real-time documentation content: dynamically returns corresponding official integration guides based on the selected goals.
+Returns:
+- content: [{ type: 'text', text: documentation content or explanatory text }]
 
-LLM must prioritize and exclusively use the real-time content returned by this tool to generate code, avoiding accessing external URLs on its own.
-
-【Mandatory Constraints】:
-1. Platform Selection Constraint: If the user does not explicitly specify a platform, or the intent is unclear, the 'present_framework_choice' tool must be called first to guide the user to choose among flutter, android, and ios.
-2. Result Recording Constraint: After TUIKit component integration is completed and the project starts successfully, the 'record_result' tool must be called to record the integration result.
-
-【Supported Platforms】: flutter, android, ios.
+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.
 `;
 const PARAMETER_DESCRIPTIONS = {
-    framework: 'Native chat TUIKit platform type. Options: flutter (Flutter cross-platform), android (Android native), ios (iOS native).',
-    goals: "List of feature goals requested by the user. Options: ['full-featured'] (standard application), ['chat-only'] (customer service/consultation/popup).",
+    framework: 'Target platform. The parameter name must be framework. Do not use platform. Allowed values: flutter | android | ios.',
+    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.",
 };
 export const GET_NATIVE_CHAT_UIKIT_INTEGRATION_DEFINITION = {
     name: 'get_native_chat_uikit_integration',

package/tools/definitions/get_native_chat_uikit_integration_def.js.map

@@ -1 +1 @@
-{"version":3,"file":"get_native_chat_uikit_integration_def.js","sourceRoot":"","sources":["../../../src/tools/definitions/get_native_chat_uikit_integration_def.ts"],"names":[],"mappings":"AAAA,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;;;;;CAsBxB,CAAC;AAEF,MAAM,sBAAsB,GAAG;IAC7B,SAAS,EAAE,0HAA0H;IACrI,KAAK,EAAE,sJAAsJ;CAC9J,CAAC;AAEF,MAAM,CAAC,MAAM,4CAA4C,GAAG;IAC1D,IAAI,EAAE,mCAAmC;IACzC,WAAW,EAAE,gBAAgB;IAC7B,sBAAsB,EAAE,sBAAsB;CAC/C,CAAC"}
+{"version":3,"file":"get_native_chat_uikit_integration_def.js","sourceRoot":"","sources":["../../../src/tools/definitions/get_native_chat_uikit_integration_def.ts"],"names":[],"mappings":"AAAA,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;CAkBxB,CAAC;AAEF,MAAM,sBAAsB,GAAG;IAC7B,SAAS,EAAE,sHAAsH;IACjI,KAAK,EAAE,sGAAsG;IAC7G,MAAM,EAAE,mHAAmH;CAC5H,CAAC;AAEF,MAAM,CAAC,MAAM,4CAA4C,GAAG;IAC1D,IAAI,EAAE,mCAAmC;IACzC,WAAW,EAAE,gBAAgB;IAC7B,sBAAsB,EAAE,sBAAsB;CAC/C,CAAC"}

package/tools/definitions/get_native_livekit_core_features_def.js

@@ -0,0 +1,34 @@
+const TOOL_DESCRIPTION = `
+Purpose:
+Return Native LiveKit Core feature-extension docs based on AtomicXCore SDK for adding interactive or effect features to an existing live streaming or voice room app.
+
+Typical use cases:
+Native LiveKit Core, AtomicXCore, no-UI SDK, core SDK, co_guest, co_host, co-guest interaction, PK, audience management, seat management, member list, live streaming, voice room, beauty, audio effects, barrage, gifts, BaseBeautyStore, AudioEffectStore, BarrageStore, GiftStore, add interactive features, add live room effects
+
+Input:
+- scenario: live | voice
+- framework: android | ios | flutter | uni-app
+- 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 }]
+
+Boundaries:
+- If the user has not specified a platform or framework, call 'present_framework_choice' first.
+- Use this tool for feature extensions on an existing AtomicXCore-based live streaming or voice room app.
+- It is not for base publishing, viewing, or room-list integration.
+- 'base_beauty', 'audio_effect', 'barrage', and 'gift' currently apply only when scenario=live.
+`;
+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.',
+    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: co_guest_interaction | co_host_interaction | audience_list | base_beauty | audio_effect | barrage | gift.',
+    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_FEATURES_DEFINITION = {
+    name: 'get_native_livekit_core_features',
+    description: TOOL_DESCRIPTION,
+    parameter_descriptions: PARAMETER_DESCRIPTIONS,
+};
+//# sourceMappingURL=get_native_livekit_core_features_def.js.map

package/tools/definitions/get_native_livekit_core_features_def.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"get_native_livekit_core_features_def.js","sourceRoot":"","sources":["../../../src/tools/definitions/get_native_livekit_core_features_def.ts"],"names":[],"mappings":"AAAA,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;;;;CAqBxB,CAAC;AAEF,MAAM,sBAAsB,GAAG;IAC7B,QAAQ,EAAE,2LAA2L;IACrM,SAAS,EAAE,gIAAgI;IAC3I,KAAK,EAAE,yIAAyI;IAChJ,MAAM,EAAE,mHAAmH;CAC5H,CAAC;AAEF,MAAM,CAAC,MAAM,2CAA2C,GAAG;IACzD,IAAI,EAAE,kCAAkC;IACxC,WAAW,EAAE,gBAAgB;IAC7B,sBAAsB,EAAE,sBAAsB;CAC/C,CAAC"}

package/tools/definitions/get_native_livekit_core_integration_def.js

@@ -0,0 +1,34 @@
+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:
+Native LiveKit Core, AtomicXCore, no-UI SDK, core SDK, live streaming, voice room, publish, watch, room list, Android, iOS, Flutter, uni-app, live, voice, set up the base live flow, set up the base voice room flow
+
+Input:
+- scenario: live | voice
+- framework: android | ios | flutter | uni-app
+- 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 }]
+
+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.
+`;
+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.',
+    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.',
+    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 = {
+    name: 'get_native_livekit_core_integration',
+    description: TOOL_DESCRIPTION,
+    parameter_descriptions: PARAMETER_DESCRIPTIONS,
+};
+//# sourceMappingURL=get_native_livekit_core_integration_def.js.map

package/tools/definitions/get_native_livekit_core_integration_def.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"get_native_livekit_core_integration_def.js","sourceRoot":"","sources":["../../../src/tools/definitions/get_native_livekit_core_integration_def.ts"],"names":[],"mappings":"AAAA,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;;;;CAqBxB,CAAC;AAEF,MAAM,sBAAsB,GAAG;IAC7B,QAAQ,EAAE,2LAA2L;IACrM,SAAS,EAAE,gIAAgI;IAC3I,KAAK,EAAE,gFAAgF;IACvF,MAAM,EAAE,mHAAmH;CAC5H,CAAC;AAEF,MAAM,CAAC,MAAM,8CAA8C,GAAG;IAC5D,IAAI,EAAE,qCAAqC;IAC3C,WAAW,EAAE,gBAAgB;IAC7B,sBAAsB,EAAE,sBAAsB;CAC/C,CAAC"}

package/tools/definitions/get_native_trtc_sdk_docs_def.js

@@ -0,0 +1,32 @@
+const TOOL_DESCRIPTION = `
+Purpose:
+Return one Native TRTC SDK documentation domain for a specific platform, suitable for core API, type definitions, callbacks, statistics, audio effects, beauty, device control, and error code lookup.
+
+Typical use cases:
+TRTC SDK, real-time audio/video, interactive live streaming, multi-user calling, screen sharing, recording, co-guest, PK, Android, iOS, C++, enter room, exit room, local preview, remote rendering, callbacks, event listeners, parameter structures, encoding params, statistics, audio effects, beauty, device management, error code, specific error code, TXLiteAVCode, what does this error code mean, how to handle this error code
+
+Input:
+- framework: android | ios | c++
+- intent: core_api | type_def | callback | statistics | audio_effect | beauty | device | error_code
+- 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 tool only returns Native TRTC SDK docs. It is not for UIKit integration or platform selection.
+- Each call returns only one documentation domain for one platform. It does not merge all docs for a platform.
+- If a specific error code is already known, prefer the error_code intent.
+`;
+const PARAMETER_DESCRIPTIONS = {
+    framework: 'Target platform. The parameter name must be framework. Do not use platform. Allowed values: android | ios | c++.',
+    intent: 'Documentation domain. Allowed values: core_api | type_def | callback | statistics | audio_effect | beauty | device | error_code.',
+    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_TRTC_SDK_DOCS_DEFINITION = {
+    name: 'get_native_trtc_sdk_docs',
+    description: TOOL_DESCRIPTION,
+    parameter_descriptions: PARAMETER_DESCRIPTIONS,
+};
+//# sourceMappingURL=get_native_trtc_sdk_docs_def.js.map

package/tools/definitions/get_native_trtc_sdk_docs_def.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"get_native_trtc_sdk_docs_def.js","sourceRoot":"","sources":["../../../src/tools/definitions/get_native_trtc_sdk_docs_def.ts"],"names":[],"mappings":"AAAA,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;;;CAoBxB,CAAC;AAEF,MAAM,sBAAsB,GAAG;IAC7B,SAAS,EAAE,kHAAkH;IAC7H,MAAM,EAAE,kIAAkI;IAC1I,MAAM,EAAE,mHAAmH;CAC5H,CAAC;AAEF,MAAM,CAAC,MAAM,mCAAmC,GAAG;IACjD,IAAI,EAAE,0BAA0B;IAChC,WAAW,EAAE,gBAAgB;IAC7B,sBAAsB,EAAE,sBAAsB;CAC/C,CAAC"}

package/tools/definitions/get_usersig_def.js

@@ -1,32 +1,27 @@
 const TOOL_DESCRIPTION = `
-[CORE FUNCTION]: \n
-Securely generates the UserSig (User Signature) credential for logging into Tencent Cloud applications, using the SDKAppID and secretKey configured by the user via MCP environment variables. \n
-Applicable to all Tencent Cloud application scenarios that require SDKAppID, userID, and UserSig for authentication, including: Instant Messaging (IM) and Real-Time Communication (TRTC). \n
+Purpose:
+Generate a test userSig from the MCP environment variables SDKAppID and secretKey for local IM or TRTC testing.
 
-[REQUIRED PARAMETERS]: \n
-- userID \n
+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
 
-[KEYWORDS]: userSig, IM, TRTC, SDKAppID, secretKey, userID, User Signature, Login Credential, Account Information, Tencent Cloud Login \n
+Input:
+- userID
 
-[CRITICAL SECURITY AND CONSTRAINTS]: \n
-1. Configuration Guidance: \n
-  - If SDKAppID and secretKey are not configured, the tool will fail to execute. \n
-  - The user MUST be guided to configure SDKAppID and secretKey via MCP environment variables, and then attempt to call this tool again. \n
-2. Key Sources: \n
-  - For Instant Messaging (IM) applications: Obtain SDKAppID and secretKey from the Chat Console (https://console.trtc.io/). \n
-  - For Real-Time Communication (TRTC) applications: Obtain SDKAppID and secretKey from the **TRTC Console** (https://console.trtc.io/). \n
-3. Security Warning: \n
-  - Generating UserSig on the frontend is insecure. The user MUST be reminded that UserSig must be generated on a backend service before the application officially goes live. \n
-4. Prohibited Actions: \n
-  - DO NOT instruct the user to manually generate UserSig in the console and paste it into the code. \n
-  - DO NOT provide frontend code implementations for UserSig generation.
+Returns:
+- content: [{ type: 'text', text: userSig result or an error message }]
+
+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.
 `;
-const PARAMETER_DESCRIPTIONS = {
-    userID: 'The User ID for which the UserSig needs to be generated (required parameter).',
-};
 export const GET_USERSIG_DEFINITION = {
     name: 'get_usersig',
     description: TOOL_DESCRIPTION,
-    parameter_descriptions: PARAMETER_DESCRIPTIONS,
+    parameter_descriptions: {
+        userID: 'The userID used to log in to the Tencent Cloud application.',
+    },
 };
 //# sourceMappingURL=get_usersig_def.js.map

package/tools/definitions/get_usersig_def.js.map

@@ -1 +1 @@
-{"version":3,"file":"get_usersig_def.js","sourceRoot":"","sources":["../../../src/tools/definitions/get_usersig_def.ts"],"names":[],"mappings":"AAAA,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;;;;;CAsBxB,CAAC;AAEF,MAAM,sBAAsB,GAAG;IAC7B,MAAM,EAAE,+EAA+E;CACxF,CAAC;AAEF,MAAM,CAAC,MAAM,sBAAsB,GAAG;IACpC,IAAI,EAAE,aAAa;IACnB,WAAW,EAAE,gBAAgB;IAC7B,sBAAsB,EAAE,sBAAsB;CAC/C,CAAC"}
+{"version":3,"file":"get_usersig_def.js","sourceRoot":"","sources":["../../../src/tools/definitions/get_usersig_def.ts"],"names":[],"mappings":"AAAA,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;CAkBxB,CAAC;AAEF,MAAM,CAAC,MAAM,sBAAsB,GAAG;IACpC,IAAI,EAAE,aAAa;IACnB,WAAW,EAAE,gBAAgB;IAC7B,sBAAsB,EAAE;QACtB,MAAM,EAAE,6DAA6D;KACtE;CACF,CAAC"}

package/tools/definitions/get_web_call_uikit_integration_def.js

@@ -1,16 +1,24 @@
 const TOOL_DESCRIPTION = `
-[CORE FUNCTION]: Provides the integration guide for Web PC/H5 Audio/Video Call applications, specifically the TUICallKit component guide for React/Vue frameworks.\n
+Purpose:
+Return Web TUICallKit preset integration docs for setting up a complete calling experience on PC or H5.
 
-[FUNCTION]: Implements audio/video call functionality and UI similar to WeChat or WeChat Work.\n
+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
 
-[KEYWORDS]: Web PC, H5, TUICallKit, Audio/Video Call, React, Vue, Integration Guide, 'CallKit', 'Integration'.\n
+Input:
+- 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.
 
-[MANDATORY CONSTRAINTS AND PROCESS]:\n
-1. Framework Selection Constraint: If the user has not explicitly specified React or Vue, the tool MUST prioritize calling 'present_framework_choice'.\n
-2. Result Recording Constraint: After the integration is complete and the project successfully starts, the tool MUST call 'record_result' to log the integration outcome.
+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.
+- Use this tool for the main Web CallKit preset integration path. It is not for API details or feature-level settings.
 `;
 const PARAMETER_DESCRIPTIONS = {
-    framework: 'The Web Call TUIKit framework type. Options: react, vue. Used to determine which framework\'s component integration solution to provide.',
+    framework: 'Target framework. The parameter name must be framework. Do not use platform. Allowed values: react | vue.',
+    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_CALL_UIKIT_INTEGRATION_DEFINITION = {
     name: 'get_web_call_uikit_integration',

package/tools/definitions/get_web_call_uikit_integration_def.js.map

@@ -1 +1 @@
-{"version":3,"file":"get_web_call_uikit_integration_def.js","sourceRoot":"","sources":["../../../src/tools/definitions/get_web_call_uikit_integration_def.ts"],"names":[],"mappings":"AAAA,MAAM,gBAAgB,GAAG;;;;;;;;;;CAUxB,CAAC;AAEF,MAAM,sBAAsB,GAAG;IAC7B,SAAS,EAAE,0IAA0I;CACtJ,CAAC;AAGF,MAAM,CAAC,MAAM,yCAAyC,GAAG;IACvD,IAAI,EAAE,gCAAgC;IACtC,WAAW,EAAE,gBAAgB;IAC7B,sBAAsB,EAAE,sBAAsB;CAC/C,CAAC"}
+{"version":3,"file":"get_web_call_uikit_integration_def.js","sourceRoot":"","sources":["../../../src/tools/definitions/get_web_call_uikit_integration_def.ts"],"names":[],"mappings":"AAAA,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;CAiBxB,CAAC;AAEF,MAAM,sBAAsB,GAAG;IAC7B,SAAS,EAAE,2GAA2G;IACtH,MAAM,EAAE,mHAAmH;CAC5H,CAAC;AAEF,MAAM,CAAC,MAAM,yCAAyC,GAAG;IACvD,IAAI,EAAE,gCAAgC;IACtC,WAAW,EAAE,gBAAgB;IAC7B,sBAAsB,EAAE,sBAAsB;CAC/C,CAAC"}

package/tools/definitions/get_web_chat_uikit_component_detail_def.js

@@ -1,59 +1,27 @@
 const TOOL_DESCRIPTION = `
-【Core Purpose】: This is a Web Chat Application UIKit Component Detail Tool, specifically designed to provide detailed descriptions, usage instructions, and sample code for individual components in Web Chat TUIKit.
+Purpose:
+Return Web Chat UIKit component-detail docs for a single component, including props, methods, events, and integration usage.
 
-【Functional Scope】:
-1. Component Overview: Provides overview information of TUIKit component list
-2. Component Details: Retrieves detailed documentation for any component, including component properties, methods, events, usage examples, etc.
+Typical use cases:
+Web Chat UIKit, component detail, React, Vue, tuikit, chat, chat-header, conversation-list, conversation-preview, conversation-search, conversation-actions, message-list, message-input, contact-list, search, theme
 
-【Core Component Modules】: This tool covers all core components of Web Chat TUIKit, including:
+Input:
+- framework: react | vue
+- componentName: component name
+- prompt: The user's original question in full. Keep the full context. Do not compress it into keywords or a short summary.
 
-**📋 Core Component List:**
-1. **Component Overview** (component-list): Overall introduction to TUIKit component library and component list overview
-2. **Complete UIKit Set** (tuikit): Complete chat UI component set, including conversation list, chat window and all features for rapid integration of complete chat applications
-3. **Chat Window Component** (chat): Complete chat window component, including chat header, message list, message input box, suitable for scenarios requiring a complete chat window
-4. **Chat Header Component** (chat-header): Top navigation bar of chat window, displaying conversation title, avatar, action buttons, suitable for customizing chat header style and functionality
-5. **Conversation List Component** (conversation-list): Conversation list component, displaying preview information of all conversations (last message, unread count, etc.), suitable for implementing chat homepage and conversation management interface
-6. **Message List Component** (message-list): Chat message list component, displaying historical messages, supporting scroll loading and various message type rendering, suitable for customizing message display style and message bubbles
-7. **Message Input Component** (message-input): Message input box component, supporting text input, emojis, images, files and other message types, suitable for customizing message input area and extending input functionality
-8. **Contact Component** (contact-list): Contact list component, displaying friend list, group list, blacklist, etc., suitable for implementing contacts page and friend management
-9. **Search Component** (search): Global search component, supporting search for contacts, groups, chat records, suitable for implementing search functionality and quick conversation lookup
-10. **Chat Settings Component** (chat-setting): Chat settings component, managing conversation configuration (such as message do not disturb, pin, clear chat history, etc.), suitable for implementing conversation settings page and group management
-11. **Avatar Component** (avatar): User avatar component, supporting custom size, shape, default avatar, suitable for displaying user avatars and group avatars
+Returns:
+- content: [{ type: 'text', text: documentation content or explanatory text }]
 
-【Keywords】: 'component details', 'TUIKit', 'Web', 'React', 'Vue', 'component list', 'component-list', 'tuikit', 'chat', 'chat-header', 'conversation-list', 'message-list', 'message-input', 'contact-list', 'search', 'chat-setting', 'avatar', 'conversation list', 'chat window', 'chat component', 'message input', 'message list', 'contacts', 'search', 'chat settings', 'avatar', 'TUIConversation', 'TUIChat', 'TUIContact', 'ConversationList', 'MessageList', 'MessageInput', 'ChatHeader', 'ContactList', 'Search', 'ChatSetting', 'Avatar'.
-
-【Supported Frameworks】: React and Vue.
-
-【Mandatory Constraints】:
-1. Framework Selection Constraint: If the user does **not explicitly specify** React or Vue framework in the prompt, must prioritize calling the 'present_framework_choice' tool to guide the user to make a selection.
-
-2. **Component Name Must Match Exactly**: componentName parameter must be selected from the following list, fuzzy matching is not supported:
-   - 'component-list': Component overview (component list overview information)
-   - 'tuikit': Complete UIKit set (overview)
-   - 'chat': Chat window component (complete chat window)
-   - 'chat-header': Chat header component (top navigation bar)
-   - 'conversation-list': Conversation list component (conversation list)
-   - 'message-list': Message list component (historical message display)
-   - 'message-input': Message input component (input box and toolbar)
-   - 'contact-list': Contact component (friend list, group list)
-   - 'search': Search component (global search)
-   - 'chat-setting': Chat settings component (conversation configuration management)
-   - 'avatar': Avatar component (user/group avatar)
+Boundaries:
+- If the user has not specified a platform or framework, call 'present_framework_choice' first.
+- This tool is for one component and its usage details. It is not for the main Chat UIKit integration path.
+- componentName must use a supported component value.
 `;
 const PARAMETER_DESCRIPTIONS = {
-    framework: 'Framework type supported by Web Chat UIKit component details. Available values: react, vue.',
-    componentName: `Specific name of Web Chat UIKit component (using hyphenated format), available values:
-- 'component-list': Component overview (component list overview)
-- 'tuikit': Complete UIKit set (overview)
-- 'chat': Chat window component
-- 'chat-header': Chat header component
-- 'conversation-list': Conversation list component
-- 'message-list': Message list component
-- 'message-input': Message input component
-- 'contact-list': Contact component
-- 'search': Search component
-- 'chat-setting': Chat settings component
-- 'avatar': Avatar component`
+    framework: 'Target framework. The parameter name must be framework. Do not use platform. Allowed values: react | vue.',
+    componentName: 'Component name. Allowed values: component-list | tuikit | chat | chat-header | conversation-list | message-list | message-input | contact-list | search | chat-setting | avatar.',
+    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_CHAT_UIKIT_COMPONENT_DETAIL_DEFINITION = {
     name: 'get_web_chat_uikit_component_detail',