@tencent-rtc/mcp 1.3.5 → 1.3.7

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