Skip to main content
Glama

实时数据/澎湃新闻热榜

Access trending news topics from The Paper's real-time hot list to stay informed about current events and popular discussions.

Instructions

实时数据/澎湃新闻热榜

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Generic handler function used by all tools, including "实时数据/澎湃新闻热榜". It sends a POST request to https://xiaobenyang.com/api with the tool's aid (apiId) and user arguments.
    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();
    }
  • Function that registers each tool dynamically, using apiDesc.title as the tool name (e.g., "实时数据/澎湃新闻热榜"), apiDesc.apiId as aid, generated schema, and wraps the generic handler. Called in a loop for all tools from the API.
    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 apiDesc from https://xiaobenyang.com/api/{MCP_ID}, where tool names like "实时数据/澎湃新闻热榜" come from apiDesc.title.
    for (const apiDesc of apiDescList) {
        addToolXiaoBenYangApi(apiDesc.apiId.toString(),
            apiDesc.title,
            apiDesc.description ? apiDesc.description : apiDesc.title,
            convertParamsToZ(apiDesc.params));
    }
  • Dynamically generates Zod schema for tool parameters based on Java types from apiDesc.params.
    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 types (with generics) to Zod schemas, 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. However, it offers no information about what the tool does operationally (e.g., whether it retrieves, updates, or monitors data), its safety profile, rate limits, authentication needs, or output format. This complete lack of behavioral context makes it inadequate for informed tool invocation.

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 but suffers from severe under-specification. While it's only a few characters long, it fails to convey essential information, making it inefficient rather than appropriately concise. Every sentence should earn its place, but here the single phrase doesn't provide enough value to justify its existence as a helpful description.

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 the complexity implied by the tool name (likely fetching or listing hot topics from a news source), the description is incomplete. With no annotations, no output schema, and a minimal description, it doesn't provide enough context for effective use. The agent lacks information on what the tool returns, how it behaves, or its operational constraints, which is insufficient for a tool that presumably interacts with dynamic data.

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, and the input schema has 100% description coverage (though empty). With no parameters to document, the description doesn't need to compensate for any gaps. The baseline score for zero parameters is 4, as there's no parameter semantics to explain beyond what the schema already covers.

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 Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention any context, prerequisites, or comparisons with sibling tools like '实时数据/微博热搜' or '实时数据/知乎热榜'. This leaves the agent without direction on selecting the appropriate tool for different scenarios.

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