Skip to main content
Glama

实时数据/今日头条热榜

Access trending topics and popular content from Jinri Toutiao's hot list to stay informed about current discussions and viral news.

Instructions

实时数据/今日头条热榜

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Dynamically registers MCP tools loaded from https://xiaobenyang.com/api/{MCP_ID}. Each tool's name is set to apiDesc.title, so the tool '实时数据/今日头条热榜' is registered here if present in the remote API response's tools list.
    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);
            }
        });
    }
    
    for (const apiDesc of apiDescList) {
        addToolXiaoBenYangApi(apiDesc.apiId.toString(),
            apiDesc.title,
            apiDesc.description ? apiDesc.description : apiDesc.title,
            convertParamsToZ(apiDesc.params));
    }
  • Core execution logic for all tools. Called with {..., aid: toolId} to POST request to the remote API, implementing the behavior for '实时数据/今日头条热榜'.
    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();
    }
  • Converts Java-style parameter descriptions from the remote API into Zod input schemas for MCP tools.
    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 to convert Java type strings (with generics) from API descriptions into 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({});
    }
  • Helper to parse Java generic types like 'List<String>' or nested, used in Zod schema conversion.
    function parseGenericType(javaType) {
        const angleBracketIndex = javaType.indexOf('<');
        if (angleBracketIndex === -1) {
            return {base: javaType.trim(), generics: []};
        }
    
        // 提取基础类型(如 "List<String>" → "List")
        const baseType = javaType.slice(0, angleBracketIndex).trim();
        // 提取泛型参数(如 "List<String>" → "String")
        const genericsStr = javaType.slice(angleBracketIndex + 1, javaType.lastIndexOf('>')).trim();
    
        // 处理嵌套泛型(如 "Map<String, List<Integer>>")
        const generics = [];
        let balance = 0; // 用于处理嵌套 <> 的平衡
        let current = '';
        for (const char of genericsStr) {
            if (char === '<') balance++;
            if (char === '>') balance--;
            if (char === ',' && balance === 0) {
                generics.push(current.trim());
                current = '';
            } else {
                current += char;
            }
        }
        if (current) generics.push(current.trim());
    
        return {base: baseType, generics};
    }
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 fails to indicate whether this is a read or write operation, what data it returns, whether it requires authentication, any rate limits, or what format the output takes. For a tool with no annotation coverage, this represents a complete lack of behavioral transparency.

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 (a single phrase), this represents under-specification rather than effective conciseness. The description fails to convey essential information about the tool's purpose and behavior. Every word should earn its place, but here the minimal content fails to serve its fundamental purpose of helping an AI agent understand and use the tool correctly.

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 the tool name (retrieving trending data from a major platform), the lack of annotations, and no output schema, the description is completely inadequate. It provides no information about what the tool returns, how the data is structured, or any behavioral characteristics. For a data retrieval tool with no structured metadata, this description fails to provide the minimal contextual information needed for effective use.

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 the baseline score is 4. The description doesn't need to compensate for any parameter documentation gaps, and the empty input schema is self-explanatory for a parameterless tool. No additional parameter information is provided or needed in the description.

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 on when to use this tool versus alternatives. With 16 sibling tools all following the '实时数据/[platform]热榜' pattern, there is no indication of what makes this tool distinct, what context it's appropriate for, or when to 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/mcp-tools'

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