@tencent-rtc/mcp 1.3.9 → 1.4.0

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',

package/tools/definitions/get_web_chat_uikit_component_detail_def.js.map

@@ -1 +1 @@
-{"version":3,"file":"get_web_chat_uikit_component_detail_def.js","sourceRoot":"","sources":["../../../src/tools/definitions/get_web_chat_uikit_component_detail_def.ts"],"names":[],"mappings":"AAAA,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAyCxB,CAAC;AAEF,MAAM,sBAAsB,GAAG;IAC7B,SAAS,EAAE,6FAA6F;IACxG,aAAa,EAAE;;;;;;;;;;;6BAWY;CAC5B,CAAC;AAGF,MAAM,CAAC,MAAM,8CAA8C,GAAG;IAC5D,IAAI,EAAE,qCAAqC;IAC3C,WAAW,EAAE,gBAAgB;IAC7B,sBAAsB,EAAE,sBAAsB;CAC/C,CAAC"}
+{"version":3,"file":"get_web_chat_uikit_component_detail_def.js","sourceRoot":"","sources":["../../../src/tools/definitions/get_web_chat_uikit_component_detail_def.ts"],"names":[],"mappings":"AAAA,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;;CAmBxB,CAAC;AAEF,MAAM,sBAAsB,GAAG;IAC7B,SAAS,EAAE,2GAA2G;IACtH,aAAa,EAAE,kLAAkL;IACjM,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_web_chat_uikit_integration_def.js

@@ -1,29 +1,26 @@
 const TOOL_DESCRIPTION = `
-**Core Purpose**: As a professional Web/cross-platform Chat TUIKit integration assistant, this tool provides Agents with workflow action instructions and real-time aggregated latest documentation content to guide LLMs in helping users implement instant messaging (IM) functionality.
+Purpose:
+Return Web Chat UIKit integration docs for building either a full chat app or a single chat window.
 
-**Functional Goals**:
-1. full-featured: Integrate complete functionality. Includes conversation list, chat window, group management, personal center, etc. **Suitable for building WeChat/WeCom-style complete applications, or as a core Tab module in Apps.**
-2. chat-only: Integrate chat window only. **Suitable for lightweight conversation scenarios such as customer service consultations, online medical consultations, order detail page private chats, etc.**
+Typical use cases:
+Web Chat UIKit, TUIKit, IM, chat, conversation list, chat window, React, Vue, full-featured, chat-only, customer service chat, consultation chat, message entry
 
-**Keywords**:
-'Chat', 'TUIKit', 'chat', 'instant messaging', 'WeChat', 'WeCom', 'React', 'Vue', 'uniapp', 'integration', 'customer service', 'medical consultation', 'TabBar', 'message entry', 'conversation list', 'dialog box'.
+Input:
+- framework: react | vue
+- goals: [full-featured] | [chat-only]
+- prompt: The user's original question in full. Keep the full context. Do not compress it into keywords or a short summary.
 
-**Action Instructions & Workflow Guidance**:
-When handling user requests, the Agent should use the llm_code_generation_instructions_md field returned by this tool. This field contains:
-1. Core workflow instructions: Includes environment preparation, dependency installation, SDK initialization, UserSig authentication, and component version specifications.
-2. Real-time documentation content: Dynamically returns the corresponding official integration guide based on the selected goals.
+Returns:
+- content: [{ type: 'text', text: documentation content or explanatory text }]
 
-LLMs MUST prioritize and exclusively use the real-time content returned by this tool to generate code, avoiding accessing external URLs independently.
-
-**Mandatory Constraints**:
-1. Framework Selection Constraint: If the user has not explicitly specified a framework or the intent is unclear, the 'present_framework_choice' tool MUST be called first to guide the user in choosing between react, vue, and uniapp-app.
-2. Result Recording Constraint: After TUIKit component integration is complete and the project starts successfully, the 'record_result' tool MUST be called to record the integration results.
-
-**Supported Frameworks**: react, vue, uniapp-app.
+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.
 `;
 const PARAMETER_DESCRIPTIONS = {
-    framework: 'Chat TUIKit framework type. Available options: react (React Web), vue (Vue3 Web), uniapp-app (Uni-app App/H5).',
-    goals: "List of functional goals requested by the user. Available options: ['full-featured'] (standard application), ['chat-only'] (customer service/consultation/popup).",
+    framework: 'Target framework. The parameter name must be framework. Do not use platform. Allowed values: react | vue.',
+    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_WEB_CHAT_UIKIT_INTEGRATION_DEFINITION = {
     name: 'get_web_chat_uikit_integration',

package/tools/definitions/get_web_chat_uikit_integration_def.js.map

@@ -1 +1 @@
-{"version":3,"file":"get_web_chat_uikit_integration_def.js","sourceRoot":"","sources":["../../../src/tools/definitions/get_web_chat_uikit_integration_def.ts"],"names":[],"mappings":"AAAA,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;;;;;CAsBxB,CAAC;AAEF,MAAM,sBAAsB,GAAG;IAC7B,SAAS,EAAE,gHAAgH;IAC3H,KAAK,EAAE,mKAAmK;CAC3K,CAAC;AAEF,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_chat_uikit_integration_def.js","sourceRoot":"","sources":["../../../src/tools/definitions/get_web_chat_uikit_integration_def.ts"],"names":[],"mappings":"AAAA,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;CAkBxB,CAAC;AAEF,MAAM,sBAAsB,GAAG;IAC7B,SAAS,EAAE,2GAA2G;IACtH,KAAK,EAAE,sGAAsG;IAC7G,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_live_uikit_integration_def.js

@@ -1,28 +1,25 @@
 const TOOL_DESCRIPTION = `
-【CORE PURPOSE】：
-Acting as a professional Web Live UIKit Integration Assistant, this tool is dedicated to providing Agents with workflow action commands and real-time aggregated, up-to-date documentation content to guide the LLM in implementing complex live streaming features.
+Purpose:
+Return Web Live UIKit page-level integration docs for wiring live list, player, publish, and co-guest entry pages.
 
-【KEYWORDS】：'liveKit', 'TUILiveKit', 'live UIKit', 'live list', 'host streaming', 'live streaming', 'audience viewing', 'desktop PC', 'mobile H5'.
+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
 
-【ACTION COMMANDS AND WORKFLOW GUIDANCE】：
-When processing user requests, the Agent should utilize the 'llm_code_generation_instructions_md' field returned by this tool. This field includes:
-1. Core workflow instructions (from integration.md).
-2. The latest, real-time official documentation content corresponding to the user's required features (Goals).
+Input:
+- goals: feature list
+- prompt: The user's original question in full. Keep the full context. Do not compress it into keywords or a short summary.
 
-The LLM MUST prioritize and exclusively use the real-time documentation content returned by this tool for code generation, avoiding self-access to external URLs.
+Returns:
+- content: [{ type: 'text', text: documentation content or explanatory text }]
 
-1. Implement Live List Page: Guides the LLM to use the 'liveList' integration documentation for implementation.
-2. Implement Live Viewing Page: Guides the LLM to use the 'livePlayer' integration documentation for implementation.
-3. Implement Live Hosting Page: Guides the LLM to use the 'livePusher' integration to implement hosting configuration and streaming.
-4. Implement Live Co-Guesting: Guides the LLM to use the 'CoGuestPanel' component, in conjunction with 'livePusher' and 'livePlayer', for co-guesting logic integration.
-
-【FUNCTIONAL SCOPE】：
-Specifically designed for building Web live streaming applications.
-
-【SUPPORTED FRAMEWORK】：Currently supports only the Vue framework.
+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.
 `;
 const PARAMETER_DESCRIPTIONS = {
-    goals: `A list of features requested by the user for implementation, e.g., ['liveList', 'livePlayer-desk', 'livePlayer-h5']. The tool will concurrently fetch the corresponding exclusive documentation content based on this list.`
+    goals: 'Feature list. Allowed values: liveList | livePlayer-desk | livePlayer-h5 | livePusher | CoGuestPanel.',
+    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 = {
     name: 'get_web_live_uikit_integration',

package/tools/definitions/get_web_live_uikit_integration_def.js.map

@@ -1 +1 @@
-{"version":3,"file":"get_web_live_uikit_integration_def.js","sourceRoot":"","sources":["../../../src/tools/definitions/get_web_live_uikit_integration_def.ts"],"names":[],"mappings":"AAAA,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;;;;;CAsBxB,CAAC;AAEF,MAAM,sBAAsB,GAAG;IAC7B,KAAK,EAAE,6NAA6N;CACrO,CAAC;AAEF,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_live_uikit_integration_def.js","sourceRoot":"","sources":["../../../src/tools/definitions/get_web_live_uikit_integration_def.ts"],"names":[],"mappings":"AAAA,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;CAkBxB,CAAC;AAEF,MAAM,sBAAsB,GAAG;IAC7B,KAAK,EAAE,uGAAuG;IAC9G,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_livekit_api_def.js

@@ -0,0 +1,30 @@
+const TOOL_DESCRIPTION = `
+Purpose:
+Return Web LiveKit State API docs for store fields, state fields, method signatures, and reactive data access.
+
+Typical use cases:
+TUILiveKit State API, Store, State, reactive data, state field, store field, method signature, which field should I read, which method should I call, live-state, updateVideoQuality, resolution, video quality, PK config, co-guest status, host state, audience state
+
+Input:
+- framework: vue
+- prompt: The user's original question in full. Keep the full context. Do not compress it into keywords or a short summary.
+
+Returns:
+- content: [{ type: 'text', text: documentation content or explanatory text }]
+
+Boundaries:
+- Vue only.
+- Use this tool for State API, store fields, and method lookup.
+- It is not for page-level integration or entry-page wiring.
+- It is not for single-component usage details.
+`;
+const PARAMETER_DESCRIPTIONS = {
+    framework: 'Target framework. The parameter name must be framework. Do not use platform. Currently only vue is supported.',
+    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_LIVEKIT_API_DEFINITION = {
+    name: 'get_web_livekit_api',
+    description: TOOL_DESCRIPTION,
+    parameter_descriptions: PARAMETER_DESCRIPTIONS,
+};
+//# sourceMappingURL=get_web_livekit_api_def.js.map

package/tools/definitions/get_web_livekit_api_def.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"get_web_livekit_api_def.js","sourceRoot":"","sources":["../../../src/tools/definitions/get_web_livekit_api_def.ts"],"names":[],"mappings":"AAAA,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;;CAmBxB,CAAC;AAEF,MAAM,sBAAsB,GAAG;IAC7B,SAAS,EAAE,+GAA+G;IAC1H,MAAM,EAAE,mHAAmH;CAC5H,CAAC;AAEF,MAAM,CAAC,MAAM,8BAA8B,GAAG;IAC5C,IAAI,EAAE,qBAAqB;IAC3B,WAAW,EAAE,gBAAgB;IAC7B,sBAAsB,EAAE,sBAAsB;CAC/C,CAAC"}

package/tools/definitions/get_web_livekit_component_detail_def.js

@@ -0,0 +1,32 @@
+const TOOL_DESCRIPTION = `
+Purpose:
+Return Web LiveKit docs for one specific component, including usage, props, capability notes, and examples.
+
+Typical use cases:
+TUILiveKit component, Vue component, specific component, component props, component example, LiveView, LiveAudienceList, Barrage, CoGuestPanel, LiveScenePanel, StreamMixer, how do I use this component, what props does this component take
+
+Input:
+- framework: vue
+- componentName: live-view | live-audience-list | barrage | co-guest-panel | live-scene-panel | stream-mixer
+- 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:
+- Vue only.
+- Use this tool for one named component.
+- It is not for page-level integration.
+- It is not for State API, store field, or method lookup.
+`;
+const PARAMETER_DESCRIPTIONS = {
+    framework: 'Target framework. The parameter name must be framework. Do not use platform. Currently only vue is supported.',
+    componentName: 'Component name. Must use the exact file-name value: live-view | live-audience-list | barrage | co-guest-panel | live-scene-panel | stream-mixer.',
+    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_LIVEKIT_COMPONENT_DETAIL_DEFINITION = {
+    name: 'get_web_livekit_component_detail',
+    description: TOOL_DESCRIPTION,
+    parameter_descriptions: PARAMETER_DESCRIPTIONS,
+};
+//# sourceMappingURL=get_web_livekit_component_detail_def.js.map

package/tools/definitions/get_web_livekit_component_detail_def.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"get_web_livekit_component_detail_def.js","sourceRoot":"","sources":["../../../src/tools/definitions/get_web_livekit_component_detail_def.ts"],"names":[],"mappings":"AAAA,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;;;CAoBxB,CAAC;AAEF,MAAM,sBAAsB,GAAG;IAC7B,SAAS,EAAE,+GAA+G;IAC1H,aAAa,EAAE,kJAAkJ;IACjK,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_web_room_uikit_integration_def.js

@@ -1,56 +1,25 @@
 const TOOL_DESCRIPTION = `
-【Core Purpose】: As a professional Web audio/video conference TUIRoomKit (Atomicx version) integration assistant, this tool is specifically designed to provide Agent with workflow action instructions and real-time aggregated latest documentation content to guide LLM in helping users implement audio/video conference functionality.
+Purpose:
+Return Web Room UIKit preset integration docs for the main meeting entry page, room page, and default meeting app flow.
 
-⭐⭐⭐ **Default First Choice Tool** ⭐⭐⭐
-Whether users have PC or H5 mobile requirements, this tool should be **called first**! This tool provides out-of-the-box UI component solutions with completed PC + H5 responsive adaptation.
-Only when users **explicitly indicate the need for custom UI interface** should the 'get_web_room_feature_detail' tool be considered.
+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
 
-【Feature Description】:
-TUIRoomKit (Atomicx version) provides a complete audio/video conference solution by default, including:
-- **Conference Entry Page (home.vue)**: Device detection, room creation/joining functionality
-- **Conference Room Page (room.vue)**: Complete header, video layout, control bar and side panels
-- **Applicable Scenarios**: Enterprise meetings, online education, remote collaboration, multi-person video calls, etc.
+Input:
+- framework: vue
+- prompt: The user's original question in full. Keep the full context. Do not compress it into keywords or a short summary.
 
-【Platform Support】:
-- **PC**: ✅ Full feature support, including conference entry page, conference room page, device detection, screen sharing, etc.
-- **H5 Mobile**: ✅ Full support! UI components are adapted for H5, can directly use pre-built UI components in mobile browsers to implement audio/video conference functionality
+Returns:
+- content: [{ type: 'text', text: documentation content or explanatory text }]
 
-【Tool Call Priority - Important】:
-- ✅ **This tool is the default first choice**: When users say "develop conference app", "H5 conference", "PC conference", "audio/video conference" → call this tool
-- ✅ **This tool takes priority**: When users don't explicitly say they want "custom UI" → call this tool
-- ❌ **Only use get_web_room_feature_detail in the following cases**: Users explicitly say "custom interface", "implement UI myself", "don't use pre-built components", "deep customization"
-
-【Keywords】:
-'TUIRoomKit', 'Atomicx', 'audio/video conference', 'TRTC', 'Vue3', 'PC', 'H5', 'mobile', 'conference room', 'video call', 'screen sharing', 'device detection', 'room management', 'grid layout', 'sidebar layout', 'source code integration', 'atomic components', 'conference application', 'Web conference', 'mobile conference'.
-
-【Technical Features】:
-- **Source Code Integration Method**: Clone repository from GitHub and copy core source code files (not npm package method)
-- **Atomicx Atomic Component Architecture**: Developers can flexibly combine atomic components to build personalized conference interfaces
-- **PC + H5 Full Platform Support**: UI components have completed responsive adaptation, same codebase supports both PC and H5
-- **TypeScript + SCSS**: Requires TypeScript and SCSS development environment configuration
-
-【Action Instructions and Workflow Guidance】:
-When Agent processes user requirements, it 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, source code cloning and copying, routing configuration, authentication UserSig and other complete processes.
-2. Real-time documentation content: Provides the latest content of official integration guides, including all configuration details and code examples.
-
-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. **This tool is the default first choice for PC/H5 conference requirements**: When users have audio/video conference needs (whether PC or H5), call this tool first.
-2. Framework limitation: TUIRoomKit (Atomicx version) only supports Vue3 framework (Vue 3.4.21 and above), does not support Vue2.x.
-3. Source code integration method: Must clone TUIRoomKit repository from GitHub and copy core source code files, cannot use simple npm install method.
-4. Authentication credential configuration: Read SDKAppID and SDKSecretKey from MCP environment variables, configure to src/config/basic-info-config.js file.
-5. Security warning: Must inform users that client-side UserSig generation is only suitable for local testing, production environment must generate UserSig on server side.
-6. Result recording constraint: After TUIRoomKit integration is completed and project starts successfully, must call 'record_result' tool to record integration results.
-7. **Only when users explicitly request custom UI**, guide them to use 'get_web_room_feature_detail' tool. Otherwise, use this tool's UI component solution by default.
-
-【Supported Framework】: vue3 (only supports Vue 3.4.21 and above).
-
-【Supported Platforms】: PC, H5 mobile (UI components have completed responsive adaptation, ready to use out of the box).
+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.
 `;
 const PARAMETER_DESCRIPTIONS = {
-    framework: 'TUIRoomKit (Atomicx version) framework type. Fixed value: vue3 (supports PC and H5 mobile).',
+    framework: 'Target framework. The parameter name must be framework. Do not use platform. Fixed value: 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_ROOM_UIKIT_INTEGRATION_DEFINITION = {
     name: 'get_web_room_uikit_integration',

package/tools/definitions/get_web_room_uikit_integration_def.js.map

@@ -1 +1 @@
-{"version":3,"file":"get_web_room_uikit_integration_def.js","sourceRoot":"","sources":["../../../src/tools/definitions/get_web_room_uikit_integration_def.ts"],"names":[],"mappings":"AAAA,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAkDxB,CAAC;AAEF,MAAM,sBAAsB,GAAG;IAC7B,SAAS,EAAE,6FAA6F;CACzG,CAAC;AAEF,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_room_uikit_integration_def.js","sourceRoot":"","sources":["../../../src/tools/definitions/get_web_room_uikit_integration_def.ts"],"names":[],"mappings":"AAAA,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;CAkBxB,CAAC;AAEF,MAAM,sBAAsB,GAAG;IAC7B,SAAS,EAAE,gGAAgG;IAC3G,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_roomkit_feature_detail_def.js

@@ -0,0 +1,31 @@
+const TOOL_DESCRIPTION = `
+Purpose:
+Return Web RoomKit custom-feature docs for Atomicx APIs, composable state, room hooks, and single-feature modules.
+
+Typical use cases:
+Atomicx API, custom modules, composable state, room hooks, useRoomState, useDeviceState, useRoomParticipantState, useRoomView, room-state, room-view, screen-share, room-chat, virtual-background, schedule-room, single-module integration, how do I add this room feature
+
+Input:
+- framework: vue
+- goals: feature list
+- prompt: The user's original question in full. Keep the full context. Do not compress it into keywords or a short summary.
+
+Returns:
+- content: [{ type: 'text', text: documentation content or explanatory text }]
+
+Boundaries:
+- Use this tool for custom modules, Atomicx APIs, hooks, and single-feature integration.
+- It is not for the main preset meeting UI integration path.
+- Vue only.
+`;
+const PARAMETER_DESCRIPTIONS = {
+    framework: 'Target framework. The parameter name must be framework. Do not use platform. Currently only vue is supported.',
+    goals: 'Feature list. Allowed values: device-detection | device-state | room-state | room-participant-state | room-view | room-chat | screen-share | schedule-room | call-user-to-room | free-beauty-panel | virtual-background.',
+    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_ROOMKIT_FEATURE_DETAIL_DEFINITION = {
+    name: 'get_web_room_feature_detail',
+    description: TOOL_DESCRIPTION,
+    parameter_descriptions: PARAMETER_DESCRIPTIONS,
+};
+//# sourceMappingURL=get_web_roomkit_feature_detail_def.js.map

package/tools/definitions/get_web_roomkit_feature_detail_def.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"get_web_roomkit_feature_detail_def.js","sourceRoot":"","sources":["../../../src/tools/definitions/get_web_roomkit_feature_detail_def.ts"],"names":[],"mappings":"AAAA,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;;CAmBxB,CAAC;AAEF,MAAM,sBAAsB,GAAG;IAC7B,SAAS,EAAE,+GAA+G;IAC1H,KAAK,EAAE,0NAA0N;IACjO,MAAM,EAAE,mHAAmH;CAC5H,CAAC;AAEF,MAAM,CAAC,MAAM,yCAAyC,GAAG;IACvD,IAAI,EAAE,6BAA6B;IACnC,WAAW,EAAE,gBAAgB;IAC7B,sBAAsB,EAAE,sBAAsB;CAC/C,CAAC"}

package/tools/definitions/get_web_trtc_sdk_api_def.js

@@ -0,0 +1,27 @@
+const TOOL_DESCRIPTION = `
+Purpose:
+Return TRTC Web SDK API docs for method lookup, room entry, publishing, remote subscription, device handling, screen sharing, networking, and exceptions.
+
+Typical use cases:
+TRTC Web SDK, RTC Engine Web SDK, WebRTC, API, which API should I use, what method should I call, method lookup, enterRoom, publish, subscribe, startLocalVideo, startLocalAudio, screen share, device, exception, error code
+
+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 }]
+
+Boundaries:
+- Use this tool for WebRTC / TRTC Web SDK API lookup, fields, and exception handling.
+- It is not for the full integration guide.
+- It is not for plugin-specific docs.
+`;
+const PARAMETER_DESCRIPTIONS = {
+    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_TRTC_SDK_API_DEFINITION = {
+    name: 'get_web_trtc_sdk_api',
+    description: TOOL_DESCRIPTION,
+    parameter_descriptions: PARAMETER_DESCRIPTIONS,
+};
+//# sourceMappingURL=get_web_trtc_sdk_api_def.js.map

package/tools/definitions/get_web_trtc_sdk_api_def.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"get_web_trtc_sdk_api_def.js","sourceRoot":"","sources":["../../../src/tools/definitions/get_web_trtc_sdk_api_def.ts"],"names":[],"mappings":"AAAA,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;CAiBxB,CAAC;AAEF,MAAM,sBAAsB,GAAG;IAC7B,MAAM,EAAE,mHAAmH;CAC5H,CAAC;AAEF,MAAM,CAAC,MAAM,+BAA+B,GAAG;IAC7C,IAAI,EAAE,sBAAsB;IAC5B,WAAW,EAAE,gBAAgB;IAC7B,sBAAsB,EAAE,sBAAsB;CAC/C,CAAC"}

package/tools/definitions/get_web_trtc_sdk_integration_def.js

@@ -0,0 +1,27 @@
+const TOOL_DESCRIPTION = `
+Purpose:
+Return TRTC Web SDK integration docs for getting started and wiring the base real-time audio/video flow.
+
+Typical use cases:
+TRTC Web SDK, RTC Engine Web SDK, WebRTC, integration, quick start, getting started, real-time audio/video, calling, enter room, publish, subscribe, set up the page, wire up the SDK, how do I get started with WebRTC here
+
+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 }]
+
+Boundaries:
+- Use this tool for the overall WebRTC / TRTC Web SDK integration path.
+- It is not for API field details.
+- It is not for plugin-specific docs.
+`;
+const PARAMETER_DESCRIPTIONS = {
+    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_TRTC_SDK_INTEGRATION_DEFINITION = {
+    name: 'get_web_trtc_sdk_integration',
+    description: TOOL_DESCRIPTION,
+    parameter_descriptions: PARAMETER_DESCRIPTIONS,
+};
+//# sourceMappingURL=get_web_trtc_sdk_integration_def.js.map

package/tools/definitions/get_web_trtc_sdk_integration_def.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"get_web_trtc_sdk_integration_def.js","sourceRoot":"","sources":["../../../src/tools/definitions/get_web_trtc_sdk_integration_def.ts"],"names":[],"mappings":"AAAA,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;CAiBxB,CAAC;AAEF,MAAM,sBAAsB,GAAG;IAC7B,MAAM,EAAE,mHAAmH;CAC5H,CAAC;AAEF,MAAM,CAAC,MAAM,uCAAuC,GAAG;IACrD,IAAI,EAAE,8BAA8B;IACpC,WAAW,EAAE,gBAAgB;IAC7B,sBAAsB,EAAE,sBAAsB;CAC/C,CAAC"}

package/tools/definitions/get_web_trtc_sdk_plugin_def.js

@@ -0,0 +1,27 @@
+const TOOL_DESCRIPTION = `
+Purpose:
+Return TRTC Web SDK plugin docs for beauty, virtual background, watermark, mixing, denoising, speech transcription, and other plugin integrations.
+
+Typical use cases:
+TRTC Web SDK plugin, plugin, Beauty, BasicBeauty, VirtualBackground, Watermark, VideoMixer, FaceDetection, AudioMixer, AIDenoiser, VoiceChanger, RealtimeTranscriber, Chorus, CDNStreaming, CrossRoom, DeviceDetector, Debug, which plugin should I use, which add-on covers this capability
+
+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 }]
+
+Boundaries:
+- Use this tool for WebRTC / TRTC Web SDK plugin capabilities.
+- It is not for the general integration guide.
+- It is not for core API details.
+`;
+const PARAMETER_DESCRIPTIONS = {
+    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_TRTC_SDK_PLUGIN_DEFINITION = {
+    name: 'get_web_trtc_sdk_plugin',
+    description: TOOL_DESCRIPTION,
+    parameter_descriptions: PARAMETER_DESCRIPTIONS,
+};
+//# sourceMappingURL=get_web_trtc_sdk_plugin_def.js.map

package/tools/definitions/get_web_trtc_sdk_plugin_def.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"get_web_trtc_sdk_plugin_def.js","sourceRoot":"","sources":["../../../src/tools/definitions/get_web_trtc_sdk_plugin_def.ts"],"names":[],"mappings":"AAAA,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;CAiBxB,CAAC;AAEF,MAAM,sBAAsB,GAAG;IAC7B,MAAM,EAAE,mHAAmH;CAC5H,CAAC;AAEF,MAAM,CAAC,MAAM,kCAAkC,GAAG;IAChD,IAAI,EAAE,yBAAyB;IAC/B,WAAW,EAAE,gBAAgB;IAC7B,sBAAsB,EAAE,sBAAsB;CAC/C,CAAC"}

package/tools/definitions/present_framework_choice_def.js

@@ -1,23 +1,35 @@
 const TOOL_DESCRIPTION = `
-[CORE FUNCTION]: A tool to force the user to select the target platform or framework when building applications with TUIKit.\n
+Purpose:
+Ask the user to choose a platform or framework before we continue, whenever the request does not clearly name one.
 
-[MANDATORY CONSTRAINT]: Every call MUST require the user to make a selection; the use of default inference or previously selected results is prohibited.
-`;
-const SELECTION_PROMPT_TEXT = `
-Please select one of the supported platforms or frameworks. Default inference results are prohibited, and user selection is mandatory on every call.\n
-1. Chat TUIKit Options:
-'react', 'vue', 'flutter', 'android', 'ios'\n
+Typical use cases:
+which platform should I use, which framework should I choose, I have not picked a platform yet, I need the integration guide, I need setup docs, quick start, how do I configure this feature, which API should I use, which component should I use, I need CallKit help, I need Chat UIKit help, I need Live UIKit help, Chat UIKit integration, Call UIKit integration, Live UIKit integration, Room UIKit integration, CallKit API, LiveKit API, WebRTC SDK integration, Native TRTC SDK integration, react, vue, flutter, android, ios, web, webrtc
+
+Trigger examples:
+- I want the Chat UIKit integration guide.
+- How do I configure the CallKit ringtone?
+- Which Chat UIKit component should I use here?
 
-2. Call Audio/Video Options:
-'react', 'vue', 'flutter', 'android', 'ios'\n
+Input:
+- product: chat | call | live | room | rtcengine | native_trtc_sdk
 
-3. rtcEngine Real-Time Communication Options:\n
-Currently only supports the WebRTC SDK.
+Returns:
+- content: [{ type: 'text', text: selectable option list }]
+
+Boundaries:
+- This tool only asks for the platform or framework choice.
+- Use this tool first when the user names the product but not the platform, or asks for setup, API, feature, or component help without saying which platform they use.
+- It does not return documentation content.
+`;
+const SELECTION_PROMPT_TEXT = `
+Show the supported platform or framework options directly to the user, ask them to pick one, and wait for their reply before calling any integration or lookup tool.
 `;
 export const PRESENT_FRAMEWORK_CHOICE_DEFINITION = {
     name: 'present_framework_choice',
     description: TOOL_DESCRIPTION,
     selectionText: SELECTION_PROMPT_TEXT,
-    parameter_descriptions: {},
+    parameter_descriptions: {
+        product: 'Target product. Allowed values: chat | call | live | room | rtcengine | native_trtc_sdk.',
+    },
 };
 //# sourceMappingURL=present_framework_choice_def.js.map

package/tools/definitions/present_framework_choice_def.js.map

@@ -1 +1 @@
-{"version":3,"file":"present_framework_choice_def.js","sourceRoot":"","sources":["../../../src/tools/definitions/present_framework_choice_def.ts"],"names":[],"mappings":"AAAA,MAAM,gBAAgB,GAAG;;;;CAIxB,CAAC;AAEF,MAAM,qBAAqB,GAAG;;;;;;;;;;CAU7B,CAAC;AAEF,MAAM,CAAC,MAAM,mCAAmC,GAAG;IACjD,IAAI,EAAE,0BAA0B;IAChC,WAAW,EAAE,gBAAgB;IAC7B,aAAa,EAAE,qBAAqB;IACpC,sBAAsB,EAAE,EAAE;CAC3B,CAAC"}
+{"version":3,"file":"present_framework_choice_def.js","sourceRoot":"","sources":["../../../src/tools/definitions/present_framework_choice_def.ts"],"names":[],"mappings":"AAAA,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;;;;;CAsBxB,CAAC;AAEF,MAAM,qBAAqB,GAAG;;CAE7B,CAAC;AAEF,MAAM,CAAC,MAAM,mCAAmC,GAAG;IACjD,IAAI,EAAE,0BAA0B;IAChC,WAAW,EAAE,gBAAgB;IAC7B,aAAa,EAAE,qBAAqB;IACpC,sBAAsB,EAAE;QACtB,OAAO,EAAE,0FAA0F;KACpG;CACF,CAAC"}