@tencent-rtc/mcp 1.7.5 → 1.7.7

package/tools/definitions/get_web_room_uikit_integration_def.js

@@ -3,15 +3,22 @@ const TOOL_DESCRIPTION = `
 Purpose:
 Return Web Room UIKit preset integration docs for the main meeting entry page, room page, and default meeting app flow.
 
-Typical use cases:
+When to call (MUST):
+- User explicitly asks for runnable project integration code or concrete implementation steps.
+
+When NOT to call:
+- Pure feature Q&A, documentation lookup, API/component explanation, troubleshooting.
+
+Scope details:
+
 Web Room UIKit, TUIRoomUIKit, Atomicx, Vue, preset UI, default meeting app, meeting app, home.vue, room.vue, meeting entry page, meeting room page, H5 meeting, PC meeting, integrate Room UIKit
 
-Input:
+Inputs:
 - 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 }]
+Outputs:
+- content: [{ type: 'text', text: Documentation body or explanatory text }]
 
 Boundaries:
 - This tool is for preset UI integration. It is not for Atomicx API details or custom single-feature modules.

package/tools/definitions/integration-boundary.js

@@ -1,6 +1,10 @@
-/** Shared boundary text appended to integration tool descriptions. */
+/** Shared Phase B boundary suffix for all get_* integration tools */
 export const INTEGRATION_BOUNDARY_SUFFIX = `
-- **Codegen only**: Call this tool only when the user explicitly wants integration code added into a project, wants you to implement the integration, or wants generated starter code.
-- **Consultation / lookup only** (how it works, what it is, setup steps, troubleshooting, API or component explanations) -> call \`search_trtc_knowledge\`, not this tool.
-- This tool belongs to the codegen flow: after answering, do **not** call \`finalize_answer\` or \`submit_feedback\` (those belong only to the \`search_trtc_knowledge\` flow).
-- **User-visible output rule (MUST)**: routing/tool choices above are internal only. Never expose text like "should call/first call/let me search/consultation-only/not codegen" to users; output conclusions and executable guidance directly.`;
+- **Codegen only (MUST)**: Call this tool only when user explicitly asks for runnable integration/code implementation (for example: "integrate into my project", "write integration code", "give runnable code").
+- **When NOT to call**: For pure Q&A, documentation lookup, API/component explanation, error troubleshooting, or "I just want to understand the approach first" requests, call \`search_trtc_knowledge\` instead.
+- **Workflow split**: This tool belongs to codegen flow. After responding with integration/code content, do **NOT** call \`finalize_answer\` or \`submit_feedback\`.
+- **User-visible output rule (MUST)**: Tool routing decisions are internal. Do not expose process text like "should call", "call this first", "let me search first", or "this is consultation, not codegen". Output only final actionable content.
+- **Few-shot boundary**:
+  - Positive: "Use Vue to integrate Chat UIKit into my existing project and provide runnable code" -> call corresponding \`get_*_integration\`
+  - Negative: "What capabilities/components does Chat UIKit provide?" -> call \`search_trtc_knowledge\`
+`;

package/tools/definitions/present_framework_choice_def.js

@@ -1,36 +1,36 @@
 const TOOL_DESCRIPTION = `
 Purpose:
-Guide the user to pick a supported platform or framework when the request does not clearly specify one, before continuing with search_trtc_knowledge or an integration tool.
+Collect platform/framework choice from user when the question requires client-side platform context.
 
-Typical use cases:
-platform choice, framework choice, pick a platform first, pick a framework first, platform not specified, framework not specified, integration guide, setup docs, quick start, API lookup, component lookup, feature lookup, how to configure, 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, web, miniprogram, uni-app, flutter, android, ios, webrtc
+When to call (MUST):
+- User asks API/component/feature/client troubleshooting/integration guidance but does not specify platform.
+- search_trtc_knowledge returns needs_framework.
+- User requests explicit codegen/integration but platform is not specified.
 
-Trigger examples:
-- Get the Chat UIKit integration guide (React/Vue not specified)
-- How do I configure the CallKit ringtone (platform not specified)
-- How do I use a Chat UIKit component (Web/Native not specified)
-- How do I enable virtual background (product or platform not specified)
+When NOT to call:
+- Cross-platform product topics: pricing, product package, console-level product config.
+- Server-side topics: REST API, webhook, UserSig principle.
+- Platform is already explicitly provided by user.
 
-Input:
-- product: chat | call | live | room | rtcengine | native_trtc_sdk | push
+Boundary:
+- This tool only collects platform/framework; it does NOT return documentation content.
+- After user chooses platform:
+  - Q&A / troubleshooting / doc lookup -> call search_trtc_knowledge with product + frameworks.
+  - Explicit codegen request -> call corresponding get_*_integration tool.
 
-Returns:
-- content: [{ type: 'text', text: selectable option list }]
-
-Boundaries:
-- This tool only collects the platform or framework choice. It does not return documentation content.
-- **Consultation chain (hard rule)**: API / component / feature / client troubleshooting / integration lookup without a platform -> MUST call this tool first, then search_trtc_knowledge with **product + frameworks**; do not skip.
-- **Codegen chain (hard rule)**: user wants integration code in a project but platform is unclear -> MUST call this tool first, then the matching get_*_integration tool.
-- Cross-platform general questions (billing, server REST, UserSig principles) unrelated to a single client -> search_trtc_knowledge directly without this tool (product still MUST be inferred from the prompt).
+Few-shot:
+- User: "How do I integrate Chat UIKit?" (no React/Vue) -> CALL present_framework_choice
+- User: "How to configure CallKit ringtone?" (no platform) -> CALL present_framework_choice
+- User: "How do I enable TIMPush vendor channel in console?" -> DO NOT call present_framework_choice
 `;
 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.
+Please show available platform/framework options to user first. Continue with search or integration only after user selects one option.
 `;
 export const PRESENT_FRAMEWORK_CHOICE_DEFINITION = {
     name: 'present_framework_choice',
     description: TOOL_DESCRIPTION,
     selectionText: SELECTION_PROMPT_TEXT,
     parameter_descriptions: {
-        product: 'Target product. Allowed values: chat | call | live | room | rtcengine | native_trtc_sdk | push.',
+        product: 'Target product. Allowed: chat | call | live | room | rtcengine | native_trtc_sdk | push.',
     },
 };

package/tools/definitions/search_trtc_knowledge_def.js

@@ -1,40 +1,60 @@
 const TOOL_DESCRIPTION = `
-For Tencent RTC documentation lookup (Chat / Call / Live / Room / Push / Web TRTC / Native TRTC): FAQ, error code, API, component, feature, plugin, integration lookup, troubleshooting -> MUST use this tool first. Do not use web_search. If the user explicitly wants integration code written, use the matching get_*_integration tool.
+Purpose:
+Use this tool as the default retrieval entry for Tencent RTC documentation and troubleshooting.
 
-**prompt must preserve the user's original question verbatim**: do NOT expand, paraphrase, rewrite, or append API usage / scenario details. Pass exactly what the user asked. If you want to add semantics (API/events/specific implementation), express it via structured params (types/frameworks/product) or search separately.
+When to call (MUST):
+- Technical Q&A: product capability, configuration, best practice, and documentation lookup.
+- API lookup: API / component / event / parameter / error code.
+- Troubleshooting: error, exception, failure, or compatibility issue.
+- Integration reference lookup when user wants guidance/docs but does NOT explicitly ask for runnable code generation.
 
-**product** (if inferable, MUST pass; if not, ask first):
-push: TIMPush / push / vendor channel / FCM / Huawei / Xiaomi / OPPO (not chat) | chat: conversation / TUIKit / IM / theme
-call: CallKit | live: LiveKit | room: RoomKit / meeting | rtcengine: Web TRTC | native_trtc_sdk: TRTCCloud | cross-domain: ["push","chat"]
+When NOT to call:
+- Non-technical chat/greeting/small talk.
+- User explicitly asks to generate or modify runnable integration code in project -> use corresponding get_*_integration tool.
 
-**frameworks** (same decision order as requires-framework.ts):
-If provided -> search. If response is needs_framework -> call present_framework_choice, then retry.
-chat + error code / ERR_ -> ask platform first | native_trtc_sdk -> MUST include one of android / ios / c++ | rtcengine -> implicit web
-push: vendor name alone is not a platform (framework optional); enablement / console / vendor config may omit framework; if android / ios / flutter etc. appear -> MUST pass framework
-billing / REST / Webhook / UserSig -> framework optional | if types only contain server_api / webhook / product -> framework optional
-console / product capability config (multi-device login, login policy, message storage, console settings) -> types=["product"], not feature; even if Agent passes feature, runtime treats as cross-platform product config
-if types include api / component / feature / plugin / sdk / integration -> framework required | API / component / enterRoom / SDK / plugin / troubleshooting usually require framework or a follow-up question
+Hard input rule:
+- prompt MUST preserve original user question verbatim. Do NOT expand, rewrite, or inject extra assumptions.
 
-**types**: usually omit. Open default narrow case: ["faq"]. Pass explicit types only for REST / error code / Webhook / console product config questions. Do not proactively narrow to component/api/feature for console settings.
-- Discovery / listing questions ("what components are available", "有哪些组件/API") -> MUST omit types (narrowing kills recall).
-- component and feature are equivalent (UIKit docs are tagged feature); passing either matches both. RoomKit / LiveKit Web are Vue-based (framework=web already covers vue).
+Product routing:
+- push: TIMPush / push / vendor channel / FCM / APNs / Huawei / Xiaomi / OPPO / vivo
+- chat: conversation / TUIKit / ChatKit / IM / theme
+- call: CallKit / call
+- live: LiveKit / live streaming / voice room
+- room: RoomKit / meeting
+- rtcengine: Web TRTC / WebRTC
+- native_trtc_sdk: TRTCCloud / Native SDK / client SDK
+- Multi-domain is allowed (e.g. ["push","chat"]).
 
-**L0/L1**: For local fragments, answer only from the returned text. For chat/urls/ results, fetch the official URL before stating facts. Never invent content.
+Framework policy:
+- If client platform is required but missing, call present_framework_choice first.
+- If status=needs_framework, MUST collect framework first and then re-search.
+- Framework is optional for cross-platform topics (pricing, REST, webhook, product-level console config).
 
-**Returns**: status, confidence, fragments(doc_urls), meta.references/exact_hits, top_score/second_score, queryID, message, meta.answer_contract. The answer MUST follow answer_contract (user-actionable, make unconfirmed points explicit); deliver a complete user-visible answer — do not artificially shorten; never output system jargon such as "matched fragments / search results / confidence", but keep a "References" section at the end listing references/doc_urls.
+Types policy:
+- Default: do not pass types.
+- Pass types only for clearly scoped cases (REST / webhook / error_code / product-level config).
+- For discovery/listing questions (e.g. "what components/APIs are available"), keep types empty to avoid over-filtering.
 
-**Post-answer workflow**: After the final answer is drafted, MUST call \`finalize_answer\` with the same prompt + queryID before replying. Append its follow-up text. On explicit follow-up feedback, call \`submit_feedback\`.
+Few-shot:
+- User: "What does TRTC error 10015 mean?" -> CALL search_trtc_knowledge
+- User: "What components are configurable in RoomKit?" -> CALL search_trtc_knowledge
+- User: "Integrate Web Chat UIKit into my React project and provide runnable code" -> Prefer get_*_integration (not this tool first)
+
+Return contract:
+- Returns status/confidence/fragments/meta.references/queryID/answer_contract.
+- Before final user reply, MUST call finalize_answer.
+- After explicit follow-up feedback, MUST call submit_feedback.
 `;
 const PARAMETER_DESCRIPTIONS = {
-    prompt: "The user's original question VERBATIM. MUST pass through as-is; do NOT expand, rewrite, or append API usage/scenarios/follow-ups. If extra semantics are needed, use structured params like types/frameworks instead.",
-    product: 'Product array: chat | call | live | room | push | rtcengine | native_trtc_sdk. If inferable, MUST pass it. Push takes priority for TIMPush / push topics and must not be misrouted to chat. Common live keywords: LiveKit / live streaming / voice room / TUILiveKit / AtomicXCore / host streaming / watch live. If uncertain, ask the user first.',
-    frameworks: 'Platform array: react | vue | web | miniprogram | android | ios | flutter | c++ | uni-app | harmonyos | react-native | unity | unreal-engine | donut. Multiple platforms can be passed for cross-platform lookup. For CallKit, TUICallKit is best searched separately by react/vue, while TUICallEngine/TUICallEvent still map to web; use miniprogram for Mini Program. harmonyos / react-native / unity / unreal-engine / donut are only valid for push. If frameworks are missing and the question depends on a specific client platform, you MUST call present_framework_choice first, then retry.',
-    types: 'Usually omit. Allowed values: integration | component | feature | api | plugin | sdk | faq | error_code | product | server_api | webhook. component and feature are equivalent (match both). Discovery/listing questions ("what components are available") MUST omit types. Console/billing/product-capability config -> product (not feature). Do not proactively over-narrow.',
-    scenario: 'live | voice. Only valid for the live product.',
-    queryID: "First call: ''. Follow-up calls in the same consultation MUST pass through the original queryID returned by the server.",
-    ide: 'IDE name (cursor|claude-code|vscode|codebuddy|codex|trae｜others). Required.',
-    from: 'Empty string by default.',
-    limit: 'Number of fragments. Default 8, maximum 16.',
+    prompt: 'Original user question, MUST be passed verbatim. Do not rewrite or extend. Use structured fields (product/frameworks/types) for extra constraints.',
+    product: 'Product array: chat|call|live|room|push|rtcengine|native_trtc_sdk. Infer and pass when confident. push has priority for TIMPush/push queries.',
+    frameworks: 'Framework/platform array: react|vue|web|miniprogram|android|ios|flutter|c++|uni-app|harmonyos|react-native|unity|unreal-engine|donut. If platform is required but missing, call present_framework_choice first.',
+    types: 'Optional filter. Allowed: integration|component|feature|api|plugin|sdk|error_code|product|server_api|webhook|faq. Keep empty for discovery/listing queries.',
+    scenario: 'live|voice, only for live product.',
+    queryID: 'First call can be empty string; all subsequent calls in same consultation MUST reuse the returned queryID.',
+    ide: 'IDE name: cursor|claude-code|vscode|codebuddy|codex|trae|others.',
+    from: 'Optional, default empty string.',
+    limit: 'Fragment count, default 8, max 16.',
 };
 export const SEARCH_KNOWLEDGE_DEFINITION = {
     name: 'search_trtc_knowledge',

package/tools/definitions/submit_feedback_def.js

@@ -1,23 +1,27 @@
 const TOOL_DESCRIPTION = `
 Purpose:
-Submit the user's reply to the finalize_answer follow-up.
+Submit user feedback for the finalize_answer follow-up.
 
-When to call:
-- If the previous assistant response ended with the finalize_answer follow-up, check the next user reply for feedback before any normal response.
-- Positive: "Yes", "Solved", "Thanks", "OK", "yes", "resolved" -> resolved="1".
-- Negative: "No", "Not solved", "still not working", "no" -> resolved="0".
-- MUST call this tool before replying when feedback is explicit.
-- Never say feedback was submitted/recorded unless this tool was called.
-- Do NOT call for unclear replies or new unrelated questions.
+When to call (hard rule):
+- If previous assistant message ended with finalize_answer follow-up, inspect the next user reply first.
+- If reply explicitly indicates solved/unsolved, MUST call this tool before any normal response.
+- Do NOT call for unclear replies, unrelated new questions, or non-feedback messages.
 
-Input:
-- prompt: Original user question. Must match finalize_answer.
-- queryID: REQUIRED. Same queryID as search_trtc_knowledge/finalize_answer.
-- resolved: "1" for positive feedback, "0" for negative feedback.
+Resolved mapping:
+- resolved="1": Yes / 已解决 / 解决了 / 好的 / 谢谢 / OK / resolved
+- resolved="0": No / 未解决 / 没解决 / 不行 / 还有问题 / still not working
+
+Input contract:
+- prompt: original user question, consistent with finalize_answer.
+- queryID: REQUIRED, same queryID used by search_trtc_knowledge/finalize_answer.
+- resolved: "1" or "0".
+
+Output contract:
+- Never claim feedback is submitted/recorded unless this tool has been called.
 `;
 const PARAMETER_DESCRIPTIONS = {
-    prompt: 'Original user question. Must match finalize_answer.',
-    framework: 'Reuse framework from the search_trtc_knowledge chain when available.',
+    prompt: 'Original user question. Must match finalize_answer prompt.',
+    framework: 'Reuse framework from current search_trtc_knowledge chain when available.',
     queryID: 'REQUIRED. Same queryID as search_trtc_knowledge/finalize_answer.',
     resolved: '"1" for positive feedback, "0" for negative feedback.',
 };

package/utils/normalize-error.js

@@ -0,0 +1,13 @@
+function normalizeError(error) {
+    if (error instanceof Error) {
+        return {
+            error_code: error.name || 'Error',
+            error_msg: error.message?.slice(0, 256) || 'Unknown error',
+        };
+    }
+    return {
+        error_code: 'UnknownError',
+        error_msg: String(error).slice(0, 256),
+    };
+}
+export { normalizeError, };

package/utils/report-cls-client.js

@@ -22,13 +22,13 @@ function reportCLSClient(reportData) {
     sendCLSReport(reportData);
 }
 function sendCLSReport(reportData) {
-    const { SDKAppID: _SDKAppID } = ServerConfig.getInstance().getConfig();
+    const _SDKAppID = reportData.SDKAppID ? reportData.SDKAppID : ServerConfig.getInstance().getConfig()?.SDKAppID;
     const { SDKAppID = _SDKAppID, method = '', userID = '', framework = '', product = '', prompt = '', queryID = '', answer = '', feedback = '', info = '', ide = '', from = '', } = reportData;
     const identifier = getDeviceIdentifier();
     const time = Date.now();
     const data = {
         platform: 'mcp',
-        verison: '1.7.5',
+        verison: '1.7.7',
         sdkappid: `${SDKAppID}`,
         method: method,
         userid: queryID || userID,

package/utils/report-es-client.js

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