Skip to main content
Glama

实时数据/腾讯新闻热榜

Access real-time trending news from Tencent News to stay informed about current events and popular topics.

Instructions

实时数据/腾讯新闻热榜

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function executed for the tool '实时数据/腾讯新闻热榜'. It makes a POST request to https://xiaobenyang.com/api with the tool's aid (apiId) and user-provided arguments, using API_KEY from env.
    const calcXiaoBenYangApi = async function (fullArgs) {
        // 发起 GET 请求
        let response = await fetch('https://xiaobenyang.com/api', {
            method: 'POST',
            headers: {
                'APIKEY': process.env.API_KEY,
                'aid': fullArgs.aid
            },
            body: new URLSearchParams(fullArgs)
        });
        return await response.text();
    }
  • Dynamically registers the tool '实时数据/腾讯新闻热榜' (and others) by calling addToolXiaoBenYangApi with apiDesc.title as name, where apiDesc comes from fetched https://xiaobenyang.com/api/{MCP_ID}.
    for (const apiDesc of apiDescList) {
        addToolXiaoBenYangApi(apiDesc.apiId.toString(),
            apiDesc.title,
            apiDesc.description ? apiDesc.description : apiDesc.title,
            convertParamsToZ(apiDesc.params));
    }
  • Converts Java-style parameter descriptions from the API response into Zod schema for input validation of tools like '实时数据/腾讯新闻热榜'.
    const convertParamsToZ = function (params) {
        let zParams = {};
        for (const param of params) {
            let zodType = convertJavaTypeToZod(param.type)
            if (param.description) {
                zodType = zodType.describe(param.name);
            }
            if (param.required) {
                zodType = zodType.optional();
            }
    
            zParams[param.name] = zodType;
        }
        return z.object(zParams);
    }
  • Helper function that maps Java types (with generics) from API descriptions to Zod types, used in schema generation for the tool.
    function convertJavaTypeToZod(javaType) {
        // 解析泛型(如处理 "List<Integer>" 这种格式)
        const {base: baseType, generics} = parseGenericType(javaType);
    
        // 优先匹配全类名(如 "java.lang.String")
        if (JAVA_TO_ZOD_MAP[baseType]) {
            return JAVA_TO_ZOD_MAP[baseType](...generics);
        }
    
        // 若全类名未匹配,提取简单类名再匹配(如 "String" 从 "java.lang.String" 提取)
        const simpleTypeName = baseType.split('.').pop();
        if (JAVA_TO_ZOD_MAP[simpleTypeName]) {
            return JAVA_TO_ZOD_MAP[simpleTypeName](...generics);
        }
    
        // 未匹配的类型默认视为自定义对象(返回 z.object(),需手动补充)
        return z.object({});
    }
  • Registers individual tools on the FastMCP server, setting name to title (e.g., '实时数据/腾讯新闻热榜'), schema to params, and execute to the shared handler with tool-specific aid.
    const addToolXiaoBenYangApi = function (aid, title, desc, params) {
        server.addTool({
            name: title,
            description: desc,
            parameters: params,
            execute: async (args) => {
                // 合并用户输入 args 和工具专属 aid
                const fullArgs = {...args, aid: aid};
                return calcXiaoBenYangApi(fullArgs);
            }
        });
    }
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. However, the description offers no information about behavioral traits such as whether this is a read-only operation, potential rate limits, authentication needs, or what the output might contain. It fails to describe any behavior beyond the implied action of accessing data, leaving significant gaps in understanding how the tool functions.

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

Conciseness2/5

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

The description is extremely concise, consisting only of the tool name repeated. However, this under-specification is not a virtue of conciseness but a lack of necessary detail. It fails to front-load key information or provide any structured explanation, making it inefficient for helping an AI agent understand the tool's purpose and usage.

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

Completeness1/5

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

Given the complexity implied by accessing real-time data from a news source, the description is incomplete. There are no annotations, no output schema, and the description lacks details on what the tool returns, how it behaves, or any usage context. For a tool that likely involves data retrieval and potential nuances like update frequency or data format, this minimal description is inadequate and fails to provide necessary context for effective tool selection and invocation.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, meaning no parameters are documented because none exist. The description does not mention any parameters, which is appropriate since there are none to describe. It adds no semantic value beyond the schema, but given the baseline of 4 for zero parameters, this meets the standard without needing compensation.

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

Purpose2/5

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

Tautological: description restates name/title.

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

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool versus its siblings. It does not mention any context, prerequisites, or alternatives. Given the list of sibling tools (e.g., '实时数据/微博热搜', '实时数据/知乎热榜'), there is no indication of when one might choose Tencent News over other news or social media hot lists, making it misleading due to the lack of differentiation.

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/xiaobenyang-com/mcp-tools'

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