Skip to main content
Glama

实时数据/IT资讯热榜

Access trending IT news and real-time data updates to stay informed about current technology developments and industry insights.

Instructions

实时数据/IT资讯热榜

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The shared handler function for all dynamically loaded tools. It sends a POST request to 'https://xiaobenyang.com/api' using the tool-specific 'aid' and input arguments, authenticating with API_KEY.
    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();
    }
  • The function used to register each tool dynamically. Tool name is set to 'title' from the API response (which includes "实时数据/IT资讯热榜"), description, Zod parameters schema, and a wrapped execute handler that injects the 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);
            }
        });
    }
  • Loop that registers all tools by calling addToolXiaoBenYangApi for each item in the fetched apiDescList (tools data from 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 the 'params' array from the API (Java-style type descriptions) into a Zod object schema used for the tool's input parameters.
    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 converts Java type strings (including generics) to corresponding Zod validators, used in schema generation.
    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({});
    }
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. The description provides zero information about what this tool actually does - whether it retrieves, creates, modifies, or deletes data; what permissions are required; rate limits; or any other behavioral characteristics. This leaves the agent completely in the dark about how to interact with this tool.

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?

While technically concise (only 7 characters), this description represents under-specification rather than effective conciseness. The single phrase '实时数据/IT资讯热榜' fails to provide any meaningful information about the tool's purpose or usage. True conciseness requires conveying essential information efficiently, not simply being brief.

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 context of 16 similar sibling tools and no annotations or output schema, the description is completely inadequate. It fails to explain what 'IT资讯热榜' means, what data it provides, how it differs from other hot list tools, or what the agent can expect when using it. For a tool that presumably retrieves hot lists from IT information sources, this description provides no useful context.

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 tool has 0 parameters with 100% schema description coverage, so there are no parameters to document. The description doesn't need to compensate for any parameter documentation gaps. While the description doesn't add any parameter information (because there are none), the baseline for a zero-parameter tool with complete schema coverage is appropriately set at 4.

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

Purpose1/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 absolutely no guidance about when to use this tool versus its many alternatives. With 16 sibling tools that all appear to be different '热榜' (hot list) tools for various platforms, the description fails to explain what makes 'IT资讯热榜' distinct or when an agent should choose it over similar tools like '知乎热榜' or '微博热搜'.

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

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