Skip to main content
Glama
Tencent-RTC

Tencent RTC MCP Server

Official
by Tencent-RTC

get_call_faq

Get answers to common questions about building chat applications with audio and video features on mobile, web, React, and Vue platforms.

Instructions

This is a tool specifically designed to solve common problems with the Call audio and video call app. Through the tool, you can get the following: | 这是一个专门负责解决 Call 音视频通话应用常见问题的工具,通过工具您可以获取以下内容:

  1. Get answers to frequently asked questions about building chat apps on mobile (native), web, react, vue, and other related platforms or frameworks. | 1. 可以获取到移动端(native)、web 端 react、vue 等相关平台或框架搭建聊天应用的常见问题解答。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
questionYesPlease describe your issue. | 请描述你的问题
sdkAppIdYesYour application's SDKAppID. | 您的应用的 SDKAppID

Implementation Reference

  • The handler function executed when the get_call_faq tool is called. It returns a standardized content response containing the FAQ text generated by getResultText.
    }, (params) => ({
        content: [
            {
                type: 'text',
                text: getResultText(params),
            }
        ]
    }));
  • Zod-based input schema defining the expected parameters: question and sdkAppId.
    question: z.string().describe('Please describe your issue. | 请描述你的问题'),
    sdkAppId: z.string().describe(`Your application's SDKAppID. | 您的应用的 SDKAppID`)
  • Module-level registration function that defines and registers the get_call_faq tool on the MCP server.
    const registryGetCallFaqTool = (mcpServer) => {
        mcpServer.tool('get_call_faq', description, {
            question: z.string().describe('Please describe your issue. | 请描述你的问题'),
            sdkAppId: z.string().describe(`Your application's SDKAppID. | 您的应用的 SDKAppID`)
        }, (params) => ({
            content: [
                {
                    type: 'text',
                    text: getResultText(params),
                }
            ]
        }));
    };
  • Helper function that logs usage via Aegis client and retrieves the static FAQ content from documentation.
    function getResultText(params) {
        const { sdkAppId = '', question = '' } = params;
        aegisClient.report({
            name: 'get_call_faq',
            ext1: sdkAppId,
            ext2: question,
            from: 'en',
        });
        return getDocContent(['tuicallkit', 'faq']);
    }
  • tools/index.js:44-44 (registration)
    Global registration call that invokes the module's registry function to add the tool to the main MCP server instance.
    registryGetCallFaqTool(mcpServer);
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It describes what the tool returns (answers to FAQs) but doesn't disclose behavioral traits like whether it's a read-only operation, if it requires authentication, rate limits, error conditions, or what format the answers come in. The description is functional but lacks operational context needed for safe invocation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is bilingual (English and Chinese) which adds redundancy but serves localization. The structure with numbered points is clear, but the opening sentence is somewhat vague ('solve common problems with the Call audio and video call app'). It's moderately concise but could be more front-loaded with the core purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and no output schema, the description is incomplete. It doesn't explain what the return format looks like (e.g., structured answers, documentation links), error handling, or operational constraints. For a tool with 2 required parameters and no structured output documentation, more behavioral context is needed for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents both parameters (question and sdkAppId) with bilingual descriptions. The description doesn't add any additional meaning about parameters beyond what's in the schema, such as examples of good questions or how the sdkAppId is used. Baseline 3 is appropriate when schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool provides answers to frequently asked questions about building chat apps on specific platforms, which gives a general purpose. However, it's vague about what 'Call audio and video call app' refers to and doesn't clearly distinguish this tool from sibling tools like get_chat_faq or get_trtc_web_sdk_faq that likely cover similar domains.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives. The description mentions 'common problems with the Call audio and video call app' but doesn't specify what types of questions are appropriate or when to choose other FAQ tools like get_chat_faq or get_trtc_web_sdk_faq. No prerequisites or exclusions are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Tencent-RTC/mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server