@tencentcloud/sdk-mcp 1.7.4 → 1.7.6

package/tools/definitions/get_web_room_core_integration_def.js

@@ -1,40 +1,49 @@
 import { INTEGRATION_BOUNDARY_SUFFIX } from './integration-boundary.js';
 const TOOL_DESCRIPTION = `
-用途：
-返回 Web RoomKit Atomicx Core 基础集成文档，适合基于 Atomicx API 自实现会议室（无预制 UI），完成登录、房间状态与设备能力接入。
+Purpose:
+Return Web RoomKit Atomicx Core integration docs for explicit codegen implementation.
 
-典型适用问题（共用触发词，可能同时命中 'get_web_room_uikit_integration' preset 工具）：
+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:
+Returns Web RoomKit Atomicx Core integration documentation for custom meeting-room implementation (no preset UI), including login, room state, and device capabilities.
+
+Common trigger lexicon (may overlap with 'get_web_room_uikit_integration' preset tool):
 Web RoomKit, TUIRoomKit, Atomicx, Vue, 集成 RoomKit, 接入会议, 会议室, meeting, room
-命中以上共用触发词时，请**先主动追问用户**："您希望使用预制 UI 快速集成（TUIRoomUIKit preset），还是基于 Atomicx API 自实现会议室？" 用户选择"自实现/Atomicx/Core"后再调用本工具；选择"预制/preset/默认 UI"则调用 'get_web_room_uikit_integration'。
+When only common triggers are hit, ask a clarification first: "Do you prefer preset UI (TUIRoomUIKit) or custom room implementation with Atomicx API?" Call this tool only after user chooses custom/Atomicx/Core; otherwise call 'get_web_room_uikit_integration'.
 
-典型适用问题（Core 专属触发词，仅命中本工具，无需追问，直接调用）：
+Core-only trigger lexicon (direct call, no clarification needed):
 Atomicx API, 自实现会议室, 自定义会议 UI, 不用预制 UI, useRoomState, useDeviceState, useLoginState, room-state, device-state, device-detection
 
-输入：
+Inputs:
 - framework: vue
 - goals: room-state | device-detection | device-state
-- prompt: 用户的原始问题全文，保留完整上下文，不要压缩成关键词摘要
+- prompt: Original user question. Keep full context; do not compress into keyword summary.
 
-返回：
-- content: [{ type: 'text', text: 文档正文或说明文本 }]
+Outputs:
+- content: [{ type: 'text', text: Documentation body or explanatory text }]
 
-边界：
-- 当用户未明确平台或框架时，应先调用 'present_framework_choice'
-- 面向 Atomicx Core 基础接入（登录 + room-state / device 模块），不负责预制 UI 页面模板
-- 屏幕分享、虚拟背景、预约会议等扩展模块 → 调用 \`search_trtc_knowledge(types=[feature])\`
-- **登录约束**：必须调用 \`get_usersig\` 获取 UserSig，再使用 \`useLoginState.login\` 登录；**禁止**在项目内实现 UserSig 生成（如 GenerateTestUserSig）
+Boundaries:
+- If platform/framework is not specified, call 'present_framework_choice' first.
+- Targets Atomicx Core baseline integration (login + room-state/device modules), not preset UI page templates.
+- For extended modules such as screen sharing, virtual background, or scheduled meeting, call \`search_trtc_knowledge(types=[feature])\`.
+- **Login constraint**: MUST call \`get_usersig\` to obtain UserSig, then use \`useLoginState.login\`; DO NOT implement local UserSig generation in project (e.g. GenerateTestUserSig).
 ${INTEGRATION_BOUNDARY_SUFFIX}
 `;
 const PARAMETER_DESCRIPTIONS = {
-    framework: '目标框架。参数名固定为 framework，禁止传 platform。固定值：vue。',
-    goals: '功能列表。可选值：room-state（房间状态）| device-detection（设备检测）| device-state（设备状态）。',
-    prompt: '用户的原始问题全文，保留完整上下文，不要压缩成关键词摘要。',
+    framework: 'Target framework. Parameter name must be framework (not platform). Fixed value: vue.',
+    goals: 'Goals list. Allowed values: room-state | device-detection | device-state.',
+    prompt: 'Original user question. Keep full context; do not compress into keyword summary.',
 };
-const ANTI_HALLUCINATION_HEADER = `本文档基于 Atomicx Core API 自实现方案，严禁照搬 TUIRoomUIKit 预制 UI 组件。\n\n`;
+const ANTI_HALLUCINATION_HEADER = `This document is based on Atomicx Core API custom implementation. DO NOT copy preset TUIRoomUIKit UI components as-is.\n\n`;
 const ANTI_HALLUCINATION_CONSTRAINT = `
 ---
-【AI 代码生成约束 - Atomicx Core 方案】
-请严格基于文档内容生成代码。登录流程 MUST 调用 get_usersig 工具获取 UserSig，再使用 useLoginState.login；禁止在项目中实现 GenerateTestUserSig 或本地 UserSig 签发逻辑。
+[AI Code Generation Constraints - Atomicx Core]
+Generate code strictly based on documented content. Login flow MUST call get_usersig to obtain UserSig, then use useLoginState.login. DO NOT implement GenerateTestUserSig or local UserSig signing logic in project.
 ---
 `;
 export const GET_WEB_ROOM_CORE_INTEGRATION_DEFINITION = {

package/tools/definitions/get_web_room_uikit_integration_def.js

@@ -1,26 +1,35 @@
 import { INTEGRATION_BOUNDARY_SUFFIX } from './integration-boundary.js';
 const TOOL_DESCRIPTION = `
-用途：
-返回 Web Room UIKit 预制 UI 集成文档，适合接入会议入口页、会议室页面和默认会议应用方案。
+Purpose:
+Return Web Room UIKit preset integration docs for explicit codegen implementation.
 
-典型适用问题：
+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:
+Returns Web Room UIKit preset integration documentation for meeting entry page, meeting room page, and default meeting app setup.
+
+Common trigger lexicon:
 Web Room UIKit, TUIRoomUIKit, Atomicx, Vue, 预制 UI, 默认会议方案, meeting app, home.vue, room.vue, 会议入口页, 会议室页面, H5 会议, PC 会议, 集成
 
-输入：
+Inputs:
 - framework: vue
-- prompt: 用户的原始问题全文，保留完整上下文，不要压缩成关键词摘要
+- prompt: Original user question. Keep full context; do not compress into keyword summary.
 
-返回：
-- content: [{ type: 'text', text: 文档正文或说明文本 }]
+Outputs:
+- content: [{ type: 'text', text: Documentation body or explanatory text }]
 
-边界：
-- 面向预制 UI 主接入，不负责 Atomicx API 或单功能模块的自定义实现细节
-- 用户要自实现 Atomicx 会议室 → 调用 'get_web_room_core_integration'
+Boundaries:
+- Targets preset UI primary integration, not Atomicx API-level or single-module custom implementation details.
+- If user wants custom Atomicx meeting-room implementation, call 'get_web_room_core_integration'.
 ${INTEGRATION_BOUNDARY_SUFFIX}
 `;
 const PARAMETER_DESCRIPTIONS = {
-    framework: '目标框架。参数名固定为 framework，禁止传 platform。固定值：vue。',
-    prompt: '用户的原始问题全文，保留完整上下文，不要压缩成关键词摘要。',
+    framework: 'Target framework. Parameter name must be framework (not platform). Fixed value: vue.',
+    prompt: 'Original user question. Keep full context; do not compress into keyword summary.',
 };
 export const GET_WEB_ROOM_UIKIT_INTEGRATION_DEFINITION = {
     name: 'get_web_room_uikit_integration',

package/tools/definitions/integration-boundary.js

@@ -1,6 +1,10 @@
-/** Phase 1 统一追加到 9× integration 工具「边界」段末尾 */
+/** Shared Phase B boundary suffix for all get_* integration tools */
 export const INTEGRATION_BOUNDARY_SUFFIX = `
-- **Codegen 专用**：仅当用户明确要求「集成进项目 / 写接入代码 / 帮我实现接入 / 生成工程代码」时调用本工具
-- **纯咨询或查阅**（怎么用、是什么、有哪些步骤、先看文档、错误排查、API/组件说明）→ 调用 \`search_trtc_knowledge\`，**不要**调用本工具
-- 本工具属 codegen 链路：作答后**不**调用 \`finalize_answer\` / \`submit_feedback\`（这两个仅属 \`search_trtc_knowledge\` 链路）
-- **用户可见输出约束（强制）**：以上链路/工具选择仅用于内部决策，禁止在对用户文本中出现“应调用/先调用/让我先搜索/我将调用某工具/属于咨询类问题/而非 codegen”等流程说明；直接输出结论与可执行内容。`;
+- **Codegen only (MUST)**: Call this tool only when user explicitly asks for runnable integration/code implementation (e.g. “接入到项目”, “写接入代码”, “直接给我可运行代码”).
+- **When NOT to call**: For pure Q&A, documentation lookup, API/component explanation, error troubleshooting, or “先了解方案/步骤” 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 “应调用/先调用/让我先搜索/我将调用某工具/属于咨询类问题/而非 codegen”. Output only the final actionable content.
+- **Few-shot boundary**:
+  - Positive: “用 Vue 把 Chat UIKit 接到我现有项目，给可运行代码” -> call corresponding \`get_*_integration\`
+  - Negative: “Chat UIKit 有哪些能力/组件？” -> call \`search_trtc_knowledge\`
+`;

package/tools/definitions/present_framework_choice_def.js

@@ -1,36 +1,36 @@
 const TOOL_DESCRIPTION = `
-用途：
-当用户未明确平台或框架时，先引导用户从受支持选项中明确选择，再继续调用 \`search_trtc_knowledge\` 或对应的 integration 工具。
+Purpose:
+Collect platform/framework choice from user when the question requires client-side platform context.
 
-典型适用问题：
-平台选择, 框架选择, 先选平台, 先选框架, 未指定平台, 未指定框架, 获取集成指南, 获取接入文档, 快速开始, 查询 API, 查询组件, 查询功能点, 怎么设置, 怎么配置, Chat UIKit 集成, Call UIKit 集成, Live UIKit 集成, Room UIKit 集成, CallKit API, LiveKit API, WebRTC SDK 集成, Native TRTC SDK 集成, 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.
 
-触发示例：
-- 获取 Chat UIKit 集成指南（未说明 React/Vue）
-- CallKit 来电铃声怎么设置（未说明平台）
-- Chat UIKit 某个组件怎么用（未说明 Web/Native）
-- 虚拟背景怎么开（未说明产品或平台）
+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.
 
-输入：
-- 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.
 
-返回：
-- content: [{ type: 'text', text: 选项列表 }]
-
-边界：
-- 只负责收集平台或框架选择，不返回文档正文
-- **咨询链路（硬规则）**：用户问 API/组件/feature/客户端排障/集成查阅，但未说明平台 → MUST **先本工具**，用户选定后再 \`search_trtc_knowledge\`（**product + frameworks**）；**禁止**跳过
-- **codegen 链路（硬规则）**：用户要集成进项目且未说明平台 → MUST **先本工具**，选定后再对应 \`get_*_integration\`
-- 跨平台通用问题（计费、服务端 REST、UserSig 原理）且与单一客户端无关 → 可直接 \`search_trtc_knowledge\`，不必经过本工具（**product 仍 MUST 从 prompt 提取**）
+Few-shot:
+- User: "Chat UIKit 怎么集成？" (no React/Vue) -> CALL present_framework_choice
+- User: "CallKit 来电铃声怎么设置？" (no platform) -> CALL present_framework_choice
+- User: "TIMPush 厂商通道怎么在控制台开通？" -> DO NOT call present_framework_choice
 `;
 const SELECTION_PROMPT_TEXT = `
-请直接向用户展示可选的平台或框架，并等待用户选择后再继续后续集成或查询。
+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: '目标产品。可选值：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,38 +1,60 @@
 const TOOL_DESCRIPTION = `
-凡 Tencent RTC 文档咨询（Chat/Call/Live/Room/Push/Web TRTC/Native TRTC）：FAQ、错误码、API、组件、feature、插件、集成查阅、排障 → MUST 先本工具。禁止 web_search。写接入代码 → get_*_integration。
+Purpose:
+Use this tool as the default retrieval entry for Tencent RTC documentation and troubleshooting.
 
-**prompt 必须原样保留用户问题**：禁止扩写、发散、改写、补充 API 用法/场景描述。用户问什么就传什么原文。若需补充语义（如 API/事件/具体实现），用 types/frameworks/product 结构化参数表达，或另行搜索。
+When to call (MUST):
+- Technical Q&A: product capability, configuration, best practice, documentation lookup.
+- API lookup: API / component / event / parameter / error code.
+- Troubleshooting: error, exception, failure, compatibility issue.
+- Integration reference lookup when user wants guidance/docs but does NOT explicitly ask for runnable code generation.
 
-**product**（能推断 MUST 传；不能确定先问用户）：
-push:TIMPush/推送/厂商/FCM/华为/小米/OPPO（≠chat）| chat:会话/TUIKit/IM/主题 | call:CallKit | live:LiveKit | room:RoomKit/会议
-rtcengine:Web TRTC | native_trtc_sdk:TRTCCloud | 跨域:["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**（requires-framework.ts 顺序）：
-已传→检索 | needs_framework→present_framework_choice后重搜
-chat+错误码/ERR_→先问platform | native→MUST 包含 android/ios/c++ 之一 | rtcengine→隐式web
-push:厂商名≠平台(可不传);开通/接入/控制台/厂商配置可不传;含android/ios/flutter等→MUST
-计费/REST/Webhook/UserSig→可不传 | types仅server_api/webhook/product→可不传
-控制台/产品能力配置（多端登录/登录策略/消息存储时长/控制台设置）→types=["product"]，勿用feature；误传feature时runtime按跨平台产品配置处理
-types含api/component/feature/plugin/sdk/integration→MUST | API/组件/enterRoom/SDK/插件/排障→MUST或先问
+Hard input rule:
+- prompt MUST preserve original user question verbatim. Do NOT expand, rewrite, or inject extra assumptions.
 
-**types**：默认不传；开放["faq"]；REST/错误码/Webhook/控制台产品配置时再传。控制台配置勿窄传component/api/feature。
-- 发现型/罗列型问题（"有哪些组件/API"、"可用组件列表"）→ MUST 省略 types（窄传会杀掉召回）。
-- component 与 feature 等价（UIKit 文档统一打 feature 标签），传任一都会同时匹配。RoomKit/LiveKit Web 基于 Vue（framework=web 已含 vue）。
+Product routing:
+- push: TIMPush / 推送 / 厂商 / FCM / APNs / 华为 / 小米 / OPPO / vivo
+- chat: 会话 / TUIKit / IM / 主题
+- call: CallKit / 通话
+- live: LiveKit / 直播 / 语聊房
+- room: RoomKit / 会议
+- rtcengine: Web TRTC / WebRTC
+- native_trtc_sdk: TRTCCloud / Native SDK / 客户端
+- Multi-domain is allowed (e.g. ["push","chat"]).
 
-**L0/L1**：本地fragments仅基于片段答；chat/urls/须fetch官网URL，禁止臆造。
+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).
 
-**返回**：status、confidence、fragments(doc_urls)、meta.references、queryID、message、meta.answer_contract。答案遵守 answer_contract(完整输出、用户可执行、未确认显式化),禁止精简,禁止输出"命中片段/检索结果/置信度/分数"等系统话术,但末尾需保留"参考文档"并列出 references/doc_urls。最终回复前 MUST 调用 finalize_answer;明确 follow-up 反馈后调用 submit_feedback。
+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. “有哪些组件/API”), keep types empty to avoid over-filtering.
+
+Few-shot:
+- User: "TRTC 报错 10015 是什么原因？" -> CALL search_trtc_knowledge
+- User: "RoomKit 有哪些可配置组件？" -> CALL search_trtc_knowledge
+- User: "帮我把 Web Chat UIKit 接进 React 项目并给可运行代码" -> 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: '用户原始问题原文，MUST 原样透传，禁止扩写/发散/补充（如补 API 用法、场景、追问）。用户没说的不写进去；需补充语义用 types/frameworks 等结构化参数表达。',
-    product: '产品数组：chat|call|live|room|push|rtcengine|native_trtc_sdk。能推断 MUST 传；push优先(TIMPush/推送→push，禁止误归chat)。live 常见关键词：LiveKit/直播/语聊房/TUILiveKit/AtomicXCore/开播/观看。不能确定先问用户。',
-    frameworks: '平台数组：react|vue|web|miniprogram|android|ios|flutter|c++|uni-app|harmonyos|react-native|unity|unreal-engine|donut。支持传多个平台用于跨端检索；CallKit 中 TUICallKit 建议按 react/vue 区分检索，TUICallEngine/TUICallEvent 仍归 web；小程序用 miniprogram；harmonyos/react-native/unity/unreal/donut仅push适用。若未传且问题依赖具体客户端平台，必须先调用 present_framework_choice 询问后重搜。',
-    types: '默认不传；开放["faq"]。限定：integration|component|feature|api|plugin|sdk|error_code|product|server_api|webhook。component 与 feature 等价（同时匹配）；发现型/罗列型问题（"有哪些组件"）MUST 省略 types。控制台/计费/产品能力配置→product（非feature）。勿主动窄传。',
-    scenario: 'live|voice，仅live产品。',
-    queryID: '首次\'\'，后续同一咨询MUST透传（见server）。',
-    ide: 'IDE名称（cursor|claude-code|vscode|codebuddy|codex|trae｜others）',
-    from: '默认空字符串。',
-    limit: '片段数，默认8，最大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/推送 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", "已解决", "解决了", "好的", "谢谢", "OK", "yes", "resolved" -> resolved="1".
-- Negative: "No", "未解决", "没解决", "不行", "还有问题", "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.',
 };