@tencent-rtc/mcp 1.3.5 → 1.3.6

package/index.js

@@ -5,10 +5,10 @@ import { ServerConfig } from './server-config.js';
 // 启动服务器
 async function main() {
     ServerConfig.getInstance();
-    const { SDKAppID } = ServerConfig.getInstance().getConfig();
-    if (isNaN(SDKAppID)) {
-        throw new Error('You have not configured the SDKAppID, or the configured SDKAppID is invalid. Please configure the correct SDKAppID through the `env` parameter in MCP.');
-    }
+    // const { SDKAppID } = ServerConfig.getInstance().getConfig();
+    // if (isNaN(SDKAppID)) {
+    //   throw new Error('You have not configured the SDKAppID, or the configured SDKAppID is invalid. Please configure the correct SDKAppID through the `env` parameter in MCP.');
+    // }
     const server = createServer();
     const transport = new StdioServerTransport();
     await server.connect(transport);

package/index.js.map

@@ -1 +1 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":";AAEA,OAAO,EAAE,oBAAoB,EAAE,MAAM,2CAA2C,CAAC;AACjF,OAAO,EAAE,YAAY,EAAE,MAAM,aAAa,CAAC;AAC3C,OAAO,EAAE,YAAY,EAAE,MAAM,oBAAoB,CAAC;AAElD,QAAQ;AACR,KAAK,UAAU,IAAI;IACjB,YAAY,CAAC,WAAW,EAAE,CAAC;IAC3B,MAAM,EAAE,QAAQ,EAAE,GAAG,YAAY,CAAC,WAAW,EAAE,CAAC,SAAS,EAAE,CAAC;IAC5D,IAAI,KAAK,CAAC,QAAQ,CAAC,EAAE,CAAC;QACpB,MAAM,IAAI,KAAK,CAAC,wJAAwJ,CAAC,CAAC;IAC5K,CAAC;IACD,MAAM,MAAM,GAAc,YAAY,EAAE,CAAC;IACzC,MAAM,SAAS,GAAG,IAAI,oBAAoB,EAAE,CAAC;IAC7C,MAAM,MAAM,CAAC,OAAO,CAAC,SAAS,CAAC,CAAC;IAChC,OAAO,CAAC,KAAK,CAAC,0CAA0C,CAAC,CAAC;AAC5D,CAAC;AAED,IAAI,EAAE,CAAC,KAAK,CAAC,CAAC,KAAK,EAAE,EAAE;IACrB,OAAO,CAAC,KAAK,CAAC,eAAe,EAAE,KAAK,CAAC,CAAC;IACtC,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;AAClB,CAAC,CAAC,CAAC"}
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":";AAEA,OAAO,EAAE,oBAAoB,EAAE,MAAM,2CAA2C,CAAC;AACjF,OAAO,EAAE,YAAY,EAAE,MAAM,aAAa,CAAC;AAC3C,OAAO,EAAE,YAAY,EAAE,MAAM,oBAAoB,CAAC;AAElD,QAAQ;AACR,KAAK,UAAU,IAAI;IACjB,YAAY,CAAC,WAAW,EAAE,CAAC;IAC3B,+DAA+D;IAC/D,yBAAyB;IACzB,+KAA+K;IAC/K,IAAI;IACJ,MAAM,MAAM,GAAc,YAAY,EAAE,CAAC;IACzC,MAAM,SAAS,GAAG,IAAI,oBAAoB,EAAE,CAAC;IAC7C,MAAM,MAAM,CAAC,OAAO,CAAC,SAAS,CAAC,CAAC;IAChC,OAAO,CAAC,KAAK,CAAC,0CAA0C,CAAC,CAAC;AAC5D,CAAC;AAED,IAAI,EAAE,CAAC,KAAK,CAAC,CAAC,KAAK,EAAE,EAAE;IACrB,OAAO,CAAC,KAAK,CAAC,eAAe,EAAE,KAAK,CAAC,CAAC;IACtC,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;AAClB,CAAC,CAAC,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tencent-rtc/mcp",
-  "version": "1.3.5",
+  "version": "1.3.6",
   "description": "Tencent Cloud MCP Server for SDK",
   "type": "module",
   "main": "index.js",

package/resource/doc/tuicallkit/flutter/workflow.md

@@ -0,0 +1,331 @@
+# Flutter TUICallKit Audio/Video Call Application Code Generation Workflow Instructions
+
+## 📋 Purpose
+
+To provide Agents with a **code generation blueprint for implementing Flutter TUICallKit core audio/video call features**, and guide Agents to **prioritize using the latest documentation content retrieved in real-time by tools**, specifically for Flutter audio/video call application scenarios.
+
+---
+
+## 🛑 Agent Execution Hard Constraints (Guardrails)
+
+Agents must strictly follow these instructions when generating code:
+
+### 0. 🚨 Core Principles (Highest Priority)
+
+- ✅ Strictly generate code according to the sample code in the integration documentation, do not modify arbitrarily
+- ✅ Fully implement login, one-on-one call, and group call features
+- ✅ Use the `get_usersig` tool to generate UserSig for test accounts
+- ✅ Use the latest version of the `tencent_calls_uikit` package (use `any` for version number)
+
+### 1. Documentation-Driven Integration
+- Strictly follow the steps in `llm_code_generation_instructions_md` returned by the tool
+- Follow best practices and sample code from the integration documentation
+
+### 2. Package Import Method
+- **Configure pubspec.yaml**: Directly edit the file to add dependencies (avoid issues with flutter command not found)
+  ```yaml
+  dependencies:
+    tencent_calls_uikit: any  # ⚠️ Use any by default to automatically get the latest version
+  ```
+- Import statement: `import 'package:tencent_calls_uikit/tencent_calls_uikit.dart';`
+- **⚠️ Prohibited**: `latest`, `^latest` and similar notations (not supported by Flutter, will cause installation failure)
+
+### 3. Silent Integration Execution
+- After all code writing is complete, automatically install dependencies and start the project in the final step
+- **Dependency Installation Method**: Directly edit `pubspec.yaml` to add `tencent_calls_uikit: any`
+- **Do not use `flutter pub add` command** (avoid failure due to flutter command not found)
+- **Flutter Command Execution Strategy (Multi-level Degradation to Ensure Success)**:
+  1. **First Priority**: Try to execute `flutter pub get` directly
+  2. **Second Priority**: If failed, use `which flutter` to get the full path and execute
+  3. **Third Priority**: If still failed, try common paths:
+     - macOS/Linux: `$HOME/flutter/bin/flutter`
+     - macOS (Homebrew): `/opt/homebrew/bin/flutter`
+  4. **Final Degradation**: If all fail, **guide user to execute manually** (see guidance below)
+- After successful startup, prompt the user to run the app on simulator or physical device
+
+#### 📋 Manual Execution Degradation Guidance
+
+**When automatic execution fails, guide the user to execute manually**:
+
+```bash
+# 1. Install dependencies
+flutter pub get
+
+# 2. iOS project additional execution
+cd ios && pod install && cd ..
+
+# 3. Start project
+flutter run
+```
+
+**Common Issues**: flutter command not found → Check PATH environment variable; pod install failed → Execute `pod repo update`
+
+### 4. Authentication Credentials Configuration (Important)
+- Call the `get_usersig` tool to get SDKAppID, UserID, and UserSig
+- Generate UserSig for 4 test accounts (user001/002/003/004)
+- Authentication information can be hardcoded during testing, but must be annotated as test-only
+- ⚠️ Security Warning: Inform users that UserSig must be generated on the server side in production environment
+
+### 5. LoginPage Implementation Constraints 🔴
+
+**⚠️ Priority Check: Whether Login Page Already Exists in Project**:
+- Before implementing the login page, **must first check whether a login page already exists in the project**
+- If a login page already exists, **must ask the user whether to execute default behavior**:
+  - **Option 1**: Use default behavior (create new LoginPage with dropdown, 3 test accounts, etc.)
+  - **Option 2**: Modify based on existing login page (keep user's UI and interaction logic, only add necessary TUICallKit login logic)
+- If user chooses Option 2, should:
+  - Keep user's existing login page UI and interaction logic
+  - Only call `TUICallKit.instance.login` for secondary login after successful login
+  - Do not force use of dropdown and 3 test accounts
+- If no login page exists in the project, or user chooses Option 1, implement according to default behavior below
+
+**Default Login Page Implementation Requirements**:
+- **Must implement login page**, including the following features:
+  1. **Dropdown to select UserID**: Provide four options: user001, user002, user003, user004
+  2. **Display SDKAppID**: Get from `get_usersig` and display (read-only, not editable)
+  3. **Auto-generate UserSig**: Automatically match from pre-generated UserSig based on selected UserID
+  4. **Login button**: Call `TUICallKit.instance.login` to login
+- **Login interface must call `TUICallKit.instance.login`**, passing complete credentials obtained from `get_usersig`
+- Automatically navigate to home page (HomePage) after successful login
+
+**LoginPage Core Implementation Points**:
+
+```dart
+// 1. Define test account mapping table (obtained from get_usersig)
+final Map<String, String> userSigMap = {
+  'user001': 'xxx', 'user002': 'xxx', 'user003': 'xxx', 'user004': 'xxx'
+};
+
+// 2. UI Components
+// - SDKAppID display (read-only TextField)
+// - UserID dropdown (DropdownButtonFormField, options generated from userSigMap.keys)
+// - Login button
+
+// 3. Login logic see integration documentation
+```
+
+### 6. HomePage Implementation Constraints 🔴
+
+**Must implement home page**, including the following features:
+
+1. **Display current logged-in UserID**
+2. **Audio/Video call features** (unified user selection):
+   - **User list (multi-select)**: Display selectable users (user002, user003, user004, excluding current logged-in user)
+   - **Smart call type determination**:
+     - Select **1 user** → Automatically initiate **one-on-one call**
+     - Select **multiple users** → Automatically initiate **group call**
+   - **Voice call button**: Call `TUICallKit.instance.calls` to initiate voice call
+   - **Video call button**: Call `TUICallKit.instance.calls` to initiate video call
+   - **Implementation method**: Use `CheckboxListTile` for multi-select, supporting single and multiple selection
+3. **Logout button**: Call `TUICallKit.instance.logout` to logout
+
+**HomePage Core Implementation Points**:
+
+```dart
+// 1. Display current logged-in user (Card + ListTile)
+
+// 2. User selection area (unified one-on-one/group calls)
+// - User list: List<String> availableUsers = ['user002', 'user003', 'user004'].where((u) => u != currentUserId).toList();
+// - Multi-select checkbox: CheckboxListTile (supports selecting 1 or multiple users)
+// - Selected users: List<String> selectedUsers = [];
+
+// 3. Call button area
+// - Voice call button: ElevatedButton
+// - Video call button: ElevatedButton
+
+// 4. Initiate call and logout logic see integration documentation
+```
+
+### 7. MaterialApp Configuration Constraints 🔴
+
+**Must add TUICallKit.navigatorObserver in MaterialApp**:
+
+```dart
+MaterialApp(
+  navigatorObservers: [TUICallKit.navigatorObserver], // ⚠️ Must be added
+  home: const LoginPage(),
+)
+```
+
+### 8. Platform Configuration 🔴
+
+**Android and iOS platform configuration please refer to integration documentation**:
+- Android obfuscation rules and Multidex configuration see integration documentation "Step 2: Project Configuration - Android" section
+- iOS permissions configuration (camera, microphone) see integration documentation "Step 2: Project Configuration - iOS" section
+
+**⚠️ Android Obfuscation Configuration Syntax Check (Important)**:
+Before configuring Android obfuscation rules, **must first check the build script type used in the project**, and choose the correct syntax based on actual situation:
+
+| Build Script File | Syntax Type | Obfuscation Configuration Syntax |
+|-------------------|-------------|----------------------------------|
+| `android/app/build.gradle` | Groovy DSL | `minifyEnabled true` |
+| `android/app/build.gradle.kts` | Kotlin DSL | `isMinifyEnabled = true` |
+
+**Check Steps**:
+1. Check the build script file name in `android/app/` directory
+2. If it's `build.gradle` → Use Groovy syntax: `minifyEnabled true`
+3. If it's `build.gradle.kts` → Use Kotlin DSL syntax: `isMinifyEnabled = true`
+
+**⚠️ iOS Podfile Platform Version Configuration (Important)**:
+When configuring iOS project, **must set minimum platform version to iOS 14.0 in `ios/Podfile`**:
+
+```ruby
+platform :ios, '14.0'
+```
+
+**Configuration Location**: Add this line at the top of Podfile, before the target configuration
+
+### 9. Flutter Project Specifications
+- Use Flutter >= 3.24.0, Dart >= 3.5.0 versions
+- Follow Flutter official code style and best practices
+
+### 10. Environment Dependency Preparation
+- Ensure user has installed Flutter SDK
+- **Flutter command execution follows multi-level degradation strategy in Section 3**
+- iOS platform requires additional execution of `cd ios && pod install && cd ..` to install Pods dependencies
+- **If automatic execution fails, must generate degradation script for user to execute manually**
+
+---
+
+## 📦 Core Version Requirements
+
+| Tool/Platform | Minimum Version Requirement |
+|---------------|----------------------------|
+| **Flutter** | >= 3.24.0 |
+| **Dart** | >= 3.5.0 |
+
+**For detailed tool version requirements (Android Studio, Gradle, JDK, Xcode, etc.), please refer to integration documentation "Preparation - Environment Requirements" section**
+
+---
+
+## 📦 Automated Execution Commands
+
+After Agent code generation is complete, execute in order:
+
+```bash
+FLUTTER_PATH=$(which flutter)  # Get actual path
+$FLUTTER_PATH pub get          # Get dependencies (based on edited pubspec.yaml)
+cd ios && pod install && cd .. # iOS dependencies (macOS)
+$FLUTTER_PATH run              # Start project
+```
+
+**Dependency Addition Method**: Directly edit `pubspec.yaml` to add `tencent_calls_uikit: any`, avoid executing `flutter pub add` command
+
+**Degradation Strategy**: `which flutter` fails → Try `$HOME/flutter/bin/flutter` → Guide user to execute manually
+
+---
+
+## 📱 Physical Device Debugging Guide (User Instructions)
+
+### iOS Physical Device Debugging
+1. Connect device via USB, trust computer
+2. **Open `ios/Runner.xcworkspace`** (not .xcodeproj)
+3. Xcode configure signing (Automatically manage signing + Apple ID + modify Bundle ID)
+4. Execute `flutter run -d ios` or `flutter devices` to view device then specify run
+5. First run requires trusting developer on device: Settings → General → VPN & Device Management → Trust
+
+### Android Physical Device Debugging
+1. Connect device via USB
+2. Enable developer mode (tap build number 7 times) + USB debugging
+3. Device authorize USB debugging (allow)
+4. Execute `adb devices` to verify connection, then `flutter run -d android`
+
+---
+
+## 🔄 Complete Automation Workflow
+
+```mermaid
+graph TD
+    A[Receive user requirements] --> B[Get Flutter actual path: which flutter]
+    B --> C[Check Flutter environment]
+    C --> D[Edit pubspec.yaml to add tencent_calls_uikit: any]
+    D --> E[Configure Android platform: obfuscation rules, Multidex]
+    E --> F[Configure iOS platform: Info.plist permissions]
+    F --> G[Configure main.dart: add navigatorObserver]
+    G --> H[Call get_usersig tool to generate UserSig for 3 accounts]
+    H --> I[Implement LoginPage: dropdown to select UserID]
+    I --> J[Implement HomePage: one-on-one and group calls]
+    J --> K[Call record_result to record integration results]
+    K --> L[Execute with full path: $FLUTTER_PATH pub get]
+    L --> M{iOS platform?}
+    M -->|Yes| N[Execute pod install]
+    M -->|No| O[Skip pod install]
+    N --> P[Guide user to connect physical device for debugging]
+    O --> P
+    P --> Q{Choose run method}
+    Q -->|Simulator| R[Execute: $FLUTTER_PATH run]
+    Q -->|iOS physical device| S[Execute: $FLUTTER_PATH run -d ios]
+    Q -->|Android physical device| T[Execute: $FLUTTER_PATH run -d android]
+    R --> U[Project startup successful]
+    S --> U
+    T --> U
+```
+
+---
+
+## 📝 Key Points Summary
+
+| Category | Requirement |
+|----------|------------|
+| **Framework Version** | Flutter >= 3.24.0, Dart >= 3.5.0 |
+| **Integration Method** | pub package method (edit `pubspec.yaml` to add `tencent_calls_uikit: any`) |
+| **Documentation Priority** | ⚠️ Strictly follow sample code in integration documentation, do not modify arbitrarily |
+| **Silent Integration** | Automatically install dependencies and start project after code writing is complete, **must use `which flutter` to get actual path** |
+| **Credential Acquisition** | ⚠️ Must use `get_usersig` tool to generate UserSig for 4 test accounts (user001/002/003/004) |
+| **Login Page** | ⚠️ Must implement dropdown to select UserID, automatically match UserSig, prohibit manual input |
+| **Home Page** | ⚠️ Must support unified user list, selecting 1 user automatically initiates one-on-one call, selecting multiple users automatically initiates group call |
+| **Security Reminder** | ⚠️ Must inform user: Client-generated UserSig is only suitable for testing, production environment must generate on server side |
+| **Result Recording** | ⚠️ Must call `record_result` tool to record results after integration is complete |
+| **Platform Configuration** | ⚠️ Android and iOS platform configuration see integration documentation "Step 2: Project Configuration" section |
+| **Navigator Observer** | ⚠️ Must add `TUICallKit.navigatorObserver` in MaterialApp |
+
+---
+
+## 🎯 Agent Execution Checklist
+
+After completing code generation, Agent must confirm all the following items:
+
+### Project Initialization
+- [ ] Edited `pubspec.yaml` to add `tencent_calls_uikit: any` dependency
+- [ ] Configured Android and iOS platforms according to integration documentation (see "Step 2: Project Configuration")
+
+### Code Generation
+- [ ] Configured `main.dart`, added `TUICallKit.navigatorObserver`
+- [ ] Called `get_usersig` tool to generate UserSig for 4 accounts
+- [ ] Implemented LoginPage (dropdown to select UserID, no manual input fields)
+- [ ] Implemented HomePage (unified user list, select 1 for one-on-one call, select multiple for group call)
+
+### Final Check
+- [ ] Called `record_result` tool to record integration results
+- [ ] Executed `flutter pub get` and `pod install` (iOS)
+- [ ] Started project, prompted user to choose device
+- [ ] Informed user: Production environment must generate UserSig on server side
+
+---
+
+## 🔗 Required Tools
+
+### `get_usersig` - Get Test Authentication Information
+Get SDKAppID, UserID (user001/002/003/004), UserSig.
+- LoginPage: Dropdown to select UserID
+- HomePage: Display selectable user list (excluding current logged-in user)
+- Prohibit manual input of SDKAppID/SecretKey/UserSig
+
+### `record_result` - Record Integration Results
+Call after completing all integration steps and successfully starting project
+
+---
+
+## 📚 Related Resource Links
+
+- **TUICallKit Flutter Pub Package**: https://pub.dev/packages/tencent_calls_uikit
+- **Tencent Cloud Real-Time Communication TRTC Console**: https://console.cloud.tencent.com/trtc
+- **Server-side UserSig Generation**: https://cloud.tencent.com/document/product/647/17275
+- **Activate TRTC Service**: https://cloud.tencent.com/document/product/647/16788
+- **Flutter Official Documentation**: https://flutter.dev/docs
+
+---
+
+**Applicable Platforms**: Flutter (Android & iOS)  
+**TUICallKit Version**: tencent_calls_uikit (latest version)  
+**Minimum Requirements**: Flutter >= 3.24.0, Dart >= 3.5.0

package/tools/call/get-native-call-integration.js

@@ -2,26 +2,42 @@ import { z } from 'zod';
 import { GET_NATIVE_CALL_UIKIT_DEFINITION } from '../definitions/get_native_call_uikit_integration_def.js';
 import { getDocContent } from '../../utils/get-doc-content.js';
 import { reportCLSClient } from '../../utils/report-cls-client.js';
-function getResultText(params) {
+import { generateStructuredResult } from '../../utils/generate-structured-result.js';
+async function getResultText(params) {
     const { framework = '' } = params;
     reportCLSClient({
         method: 'get_native_call_uikit_integration',
-        framework: framework,
+        framework,
     });
-    return getDocContent(['tuicallkit', `${framework}`]);
+    // 获取工作流指令
+    const baseInstructions = getDocContent(['tuicallkit', framework, 'workflow.md']);
+    // Call 默认全量集成,无需 goals 参数
+    const result = await generateStructuredResult({
+        baseInstructions,
+        goals: ['full-featured'], // 默认全量集成
+        framework,
+        pathMap: {
+            'full-featured': ['tuicallkit', framework, 'integration.md'],
+        },
+    });
+    return result;
 }
 const registryGetNativeCallIntegrationTool = (mcpServer) => {
     const { name, description, parameter_descriptions } = GET_NATIVE_CALL_UIKIT_DEFINITION;
     mcpServer.tool(name, description, {
         framework: z.enum(['flutter', 'android', 'ios']).describe(parameter_descriptions.framework),
-    }, (params) => ({
-        content: [
-            {
-                type: 'text',
-                text: getResultText(params),
-            }
-        ]
-    }));
+    }, async (params) => {
+        const result = await getResultText(params);
+        return {
+            content: [
+                {
+                    type: 'text',
+                    text: result.llm_code_generation_instructions_md,
+                }
+            ],
+            result: result,
+        };
+    });
 };
 export { registryGetNativeCallIntegrationTool };
 //# sourceMappingURL=get-native-call-integration.js.map

package/tools/call/get-native-call-integration.js.map

@@ -1 +1 @@
-{"version":3,"file":"get-native-call-integration.js","sourceRoot":"","sources":["../../../src/tools/call/get-native-call-integration.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AACxB,OAAO,EAAE,gCAAgC,EAAE,MAAM,yDAAyD,CAAC;AAC3G,OAAO,EAAE,aAAa,EAAE,MAAM,gCAAgC,CAAC;AAC/D,OAAO,EAAE,eAAe,EAAE,MAAM,kCAAkC,CAAC;AAEnE,SAAS,aAAa,CAAC,MAA2B;IAChD,MAAM,EAAE,SAAS,GAAG,EAAE,EAAE,GAAG,MAAM,CAAC;IAClC,eAAe,CAAC;QACd,MAAM,EAAE,mCAAmC;QAC3C,SAAS,EAAE,SAAS;KACrB,CAAC,CAAC;IACH,OAAO,aAAa,CAAC,CAAC,YAAY,EAAE,GAAG,SAAS,EAAE,CAAC,CAAC,CAAC;AACvD,CAAC;AAED,MAAM,oCAAoC,GAAG,CAAC,SAAoB,EAAE,EAAE;IACpE,MAAM,EAAE,IAAI,EAAE,WAAW,EAAE,sBAAsB,EAAE,GAAG,gCAAgC,CAAC;IACvF,SAAS,CAAC,IAAI,CACZ,IAAI,EACJ,WAAW,EACX;QACE,SAAS,EAAE,CAAC,CAAC,IAAI,CAAC,CAAC,SAAS,EAAE,SAAS,EAAE,KAAK,CAAC,CAAC,CAAC,QAAQ,CAAC,sBAAsB,CAAC,SAAS,CAAC;KAC5F,EAAE,CAAC,MAAM,EAAE,EAAE,CAAC,CAAC;QACd,OAAO,EAAE;YACP;gBACE,IAAI,EAAE,MAAM;gBACZ,IAAI,EAAE,aAAa,CAAC,MAAM,CAAC;aAC5B;SACF;KACF,CAAC,CAAC,CAAC;AACR,CAAC,CAAC;AACF,OAAO,EAAE,oCAAoC,EAAE,CAAC"}
+{"version":3,"file":"get-native-call-integration.js","sourceRoot":"","sources":["../../../src/tools/call/get-native-call-integration.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AACxB,OAAO,EAAE,gCAAgC,EAAE,MAAM,yDAAyD,CAAC;AAC3G,OAAO,EAAE,aAAa,EAAE,MAAM,gCAAgC,CAAC;AAC/D,OAAO,EAAE,eAAe,EAAE,MAAM,kCAAkC,CAAC;AACnE,OAAO,EAAE,wBAAwB,EAAE,MAAM,2CAA2C,CAAC;AAErF,KAAK,UAAU,aAAa,CAAC,MAA2B;IACtD,MAAM,EAAE,SAAS,GAAG,EAAE,EAAE,GAAG,MAAM,CAAC;IAClC,eAAe,CAAC;QACd,MAAM,EAAE,mCAAmC;QAC3C,SAAS;KACV,CAAC,CAAC;IACH,UAAU;IACV,MAAM,gBAAgB,GAAG,aAAa,CAAC,CAAC,YAAY,EAAE,SAAS,EAAE,aAAa,CAAC,CAAC,CAAC;IACjF,0BAA0B;IAC1B,MAAM,MAAM,GAAG,MAAM,wBAAwB,CAAC;QAC5C,gBAAgB;QAChB,KAAK,EAAE,CAAC,eAAe,CAAC,EAAE,SAAS;QACnC,SAAS;QACT,OAAO,EAAE;YACP,eAAe,EAAE,CAAC,YAAY,EAAE,SAAS,EAAE,gBAAgB,CAAC;SAC7D;KACF,CAAC,CAAA;IACF,OAAO,MAAM,CAAC;AAChB,CAAC;AAED,MAAM,oCAAoC,GAAG,CAAC,SAAoB,EAAE,EAAE;IACpE,MAAM,EAAE,IAAI,EAAE,WAAW,EAAE,sBAAsB,EAAE,GAAG,gCAAgC,CAAC;IACvF,SAAS,CAAC,IAAI,CACZ,IAAI,EACJ,WAAW,EACX;QACE,SAAS,EAAE,CAAC,CAAC,IAAI,CAAC,CAAC,SAAS,EAAE,SAAS,EAAE,KAAK,CAAC,CAAC,CAAC,QAAQ,CAAC,sBAAsB,CAAC,SAAS,CAAC;KAC5F,EACD,KAAK,EAAE,MAAW,EAAE,EAAE;QACpB,MAAM,MAAM,GAAG,MAAM,aAAa,CAAC,MAAM,CAAC,CAAA;QAC1C,OAAO;YACL,OAAO,EAAE;gBACP;oBACE,IAAI,EAAE,MAAM;oBACZ,IAAI,EAAE,MAAM,CAAC,mCAAmC;iBACjD;aACF;YACD,MAAM,EAAE,MAAM;SACf,CAAA;IACL,CAAC,CAAC,CAAC;AACL,CAAC,CAAC;AAEF,OAAO,EAAE,oCAAoC,EAAE,CAAC"}

package/tools/definitions/get_native_call_uikit_integration_def.js

@@ -1,17 +1,27 @@
 const TOOL_DESCRIPTION = `
-[CORE FUNCTION]: This is a Native Audio/Video Call Application Creation Tool, specialized in providing the integration guide for the TUICallKit component library on mobile (Native) platforms.\n
+【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.
 
-[FUNCTION]: This tool provides the Call UIKit component integration solution, enabling audio/video call functionality and UI similar to WeChat or WeChat Work.\n
+【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.**
 
-[SUPPORTED PLATFORMS]: flutter (Cross-platform), android (Native), ios (Native).\n
+【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'.
 
-[KEYWORDS]: native, Call, Audio/Video Call, TUICallKit, flutter, android, ios, Integration Guide.\n
+【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.
 
-[MANDATORY CONSTRAINTS]:\n
-1. Platform Selection Constraint: If the user has not specified a particular platform or framework in the prompt, the tool MUST prioritize calling 'present_framework_choice' to guide the user to make a selection.
+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.
 `;
 const PARAMETER_DESCRIPTIONS = {
-    framework: 'The platform type for the Native Call UIKit component library. Options: flutter, android, ios. The user must select one platform to create the application.',
+    framework: 'Native audio/video call TUICallKit platform type. Available values: flutter (Flutter cross-platform), android (Android native), ios (iOS native).',
 };
 export const GET_NATIVE_CALL_UIKIT_DEFINITION = {
     name: 'get_native_call_uikit_integration',

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;;;;;;;;;;;CAWxB,CAAC;AAEF,MAAM,sBAAsB,GAAG;IAC7B,SAAS,EAAE,6JAA6J;CACzK,CAAC;AAGF,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;;;;;;;;;;;;;;;;;;;;;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"}

package/utils/report-cls-client.js

@@ -6,7 +6,7 @@ function reportCLSClient(reportData) {
     const time = Date.now();
     const data = {
         platform: 'mcp',
-        verison: '1.3.5',
+        verison: '1.3.6',
         sdkappid: `${SDKAppID}`,
         method: method,
         userid: userID,

package/utils/report-es-client.js

@@ -7,7 +7,7 @@ function reportESClient(reportData) {
         report: [
             {
                 platform: 'mcp',
-                version: '1.3.5',
+                version: '1.3.6',
                 sdkappid: `${SDKAppID}`,
                 method: method,
                 userID: `${userID}`,

package/resource/doc/tuicallkit/flutter/how_to_run_flutter_callkit_demo.md

@@ -1,101 +0,0 @@
-This article will guide you on how to quickly run through the Audio and Video Call Demo. By following this document, you can have the Demo up and running in 10 minutes, and ultimately experience an Audio and Video Call feature with a complete UI interface.
-<table>
-<tr>
-<td rowspan="1" colSpan="1" >1v1 Video Call</td>
-
-<td rowspan="1" colSpan="1" >Group call</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100027164818/b8670a89190311ef957f525400f65c2a.png)</td>
-
-<td rowspan="1" colSpan="1" >![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100027164818/5866a4f4190311efa1975254005ac0ca.png)</td>
-</tr>
-</table>
-
-
-## Environment preparations
-
-### Flutter
-
-Flutter 3.0 or later.
-
-### Android 
-- Android Studio 3.5 or above.
-
-- Android devices with Android 4.1 or higher versions.
-
-
-### iOS
-- Xcode 13.0 or above.
-
-- Please ensure your project is set up with a valid developer signature.
-
-
-## Step 1: Download the Demo
-1. Download the [TUICallKit Demo](https://github.com/Tencent-RTC/TUICallKit/tree/main) source code from GitHub, or directly run the following command in the command line:
-
-   ``` bash
-     git clone 
-   ```
-2. Open the TUICallKit Flutter example in Android Studio or VSCode. The following process will take Android Studio as an example:
-
-
-   ![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100032451803/34ec5a44126311efa2935254005ac0ca.png)
-
-
-## Step 2: Configure the Demo
-1. [Activate the audio and video services](https://write.woa.com/document/140196392040579072), to obtain the **SDKAppID** and **SDKSecretKey**.
-
-
-   ![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100032451803/350369ae126311ef9fa952540019e87e.png)
-
-2. Open the `Flutter/example/lib/debug/generate_test_user_sig.dart` file and fill in the SDKAppID and SDKSecretKey obtained when [Activating the Service](https://write.woa.com/document/140196392040579072):
-
-
-   ![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100032451803/a8926a892d3911ef9bb3525400ab9413.png)
-
-
-## Step 3: Running the Demo
-1. In the top right corner of Android Studio, select the device you want to run the Demo on as shown below:
-
-
-   ![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100032451803/6e880f462d3f11efa4f552540077de32.png)
-
-2. After selecting, click Run to execute the TUICallKit Android Demo on the target device.
-
-
-   ![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100032451803/79760e132d3f11ef97da5254007d9c55.png)
-
-
-## Make the first call
-
-> **Note:**
-> 
-
-> To experience the complete audio and video calling process, please log into the Demo on two devices as two different users, with one acting as the caller and the other as the callee.
-> 
-
-1. Log in & Signup
-
-
-   Please enter the ID at the `User ID`. If your current User ID has not been used before, you will be taken to the **Signup** screen, where you can set your own avatar and nickname.
-
-
-   ![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100032451803/b51ef4631e6911ef860b52540049c929.png)
-   
-
-   > **Note:**
-   > 
-
-   > Try to avoid setting your User ID to simple strings like "1", "123", "111", as TRTC does not support the same User ID being logged into from multiple devices. Such User IDs like "1", "123", "111" are easily occupied by your colleagues during collaborative development, leading to login failures. Therefore, we recommend setting highly recognizable User IDs while debugging.
-   > 
-
-2. Make a phone call
-
-  1. The caller should click **1V1 Call** on the interface, enter the callee's User ID in the pop-up interface, and select the desired call type.
-
-  2. Click **Initiate Call**.
-
-
-      ![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100032451803/ac43fa871e6a11efbef6525400a8a0fb.png)

package/resource/doc/tuicallkit/iOS/how_to_run_iOS_callkit_demo.md

@@ -1,98 +0,0 @@
-This article will guide you on how to quickly run through the Audio and Video Call Demo. By following this document, you can have the Demo up and running in 10 minutes, and ultimately experience an Audio and Video Call feature with a complete UI interface.
-<table>
-<tr>
-<td rowspan="1" colSpan="1" >1v1 Video Call</td>
-
-<td rowspan="1" colSpan="1" >Group call</td>
-</tr>
-
-<tr>
-<td rowspan="1" colSpan="1" >![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100027164818/b8670a89190311ef957f525400f65c2a.png)</td>
-
-<td rowspan="1" colSpan="1" >![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100027164818/5866a4f4190311efa1975254005ac0ca.png)</td>
-</tr>
-</table>
-
-
-## Environment preparations
-- Xcode 13 or later.
-
-- Two iOS 13.0 or later devices.
-
-
-## Step 1: Download the Demo
-1. Download the [TUICallKit Demo](https://github.com/Tencent-RTC/TUICallKit/tree/main) source code from GitHub, or directly run the following command in the command line:
-
-   ``` bash
-     git clone 
-   ```
-2. Enter the iOS project directory in the command line:
-
-   ``` plaintext
-     cd TUICallKit/iOS/Example
-   ```
-3. Load the dependency library:
-
-   ``` plaintext
-     pod install
-   ```   
-
-   > **Note:**
-   > 
-
-   > If you haven't installed CocoaPods, you can refer to [this](https://guides.cocoapods.org/using/getting-started.html) for instructions on how to install.
-   > 
-
-
-## Step 2: Configure the Demo
-1. [Activate the audio and video services](https://write.woa.com/document/140196392040579072), to obtain the **SDKAppID** and **SDKSecretKey**.
-
-
-   ![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100032451803/54ae79bd126311ef9af4525400720cb5.png)
-
-2. Open the `/iOS/Example/Debug/GenerateTestUserSig.swift` file and enter the SDKAppID and SDKSecretKey obtained when [activating the service](https://write.woa.com/document/140196392040579072):
-
-
-   ![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100032451803/5510e016126311ef9fa952540019e87e.png)
-
-
-## Step 3: Running the Demo
-1. In XCode, select the device you want to run the Demo on as shown below:
-
-
-   ![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100032451803/54b99a2c126311ef9af4525400720cb5.png)
-
-2. After selection, click run to deploy our TUICallKit iOS Demo to the target device.
-
-
-## Make the first call
-
-> **Note:**
-> 
-
-> To experience the complete audio and video calling process, please log into the Demo on two devices as two different users, with one acting as the caller and the other as the callee.
-> 
-
-1. Log in & Signup
-
-
-   Please enter the ID at the `User ID`. If your current User ID has not been used before, you will be taken to the **Signup** screen, where you can set your own avatar and nickname.
-
-
-   ![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100032451803/e23a537b1e6a11ef91395254000a29ac.png)
-   
-
-   > **Note:**
-   > 
-
-   > Try to avoid setting your User ID to simple strings like "1", "123", "111", as TRTC does not support the same User ID being logged into from multiple devices. Such User IDs like "1", "123", "111" are easily occupied by your colleagues during collaborative development, leading to login failures. Therefore, we recommend setting highly recognizable User IDs while debugging.
-   > 
-
-2. Make a phone call
-
-  1. The caller should click **1V1 Call** on the interface, enter the callee's User ID in the pop-up interface, and select the desired call type.
-
-  2. Click **Initiate Call**.
-
-
-      ![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100032451803/e9161c071e6a11ef860b52540049c929.png)