Skip to main content
Glama

实时数据/澎湃新闻热榜

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

Instructions

实时数据/澎湃新闻热榜

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function `calcXiaoBenYangApi` that implements the logic for all dynamically loaded tools, including "实时数据/澎湃新闻热榜". It sends a POST request to https://xiaobenyang.com/api with the tool's aid and 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();
    }
  • Dynamic registration of tools from remote API descriptions. Each tool's `title` becomes the tool name (likely including "实时数据/澎湃新闻热榜"), registered with a shared execute handler that uses the 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);
            }
        });
    }
    
    for (const apiDesc of apiDescList) {
        addToolXiaoBenYangApi(apiDesc.apiId.toString(),
            apiDesc.title,
            apiDesc.description ? apiDesc.description : apiDesc.title,
            convertParamsToZ(apiDesc.params));
    }
  • Converts Java parameter descriptions from the remote API into Zod schemas for tool input validation.
    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 to convert Java type strings (including generics) to 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 (e.g., "List<String>") into base type and generics array, used in Zod 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. However, it offers no information on traits such as read-only status, rate limits, authentication needs, or output format. This is inadequate for a tool that likely involves data retrieval, leaving the agent unaware of operational constraints.

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 a single phrase that mirrors the tool name, making it under-specified rather than concise. It lacks structure and fails to front-load essential information, such as purpose or usage. While brief, it does not earn its place by adding value beyond the name.

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 tool's likely complexity (fetching hot topics from a news source) and the absence of annotations and output schema, the description is incomplete. It does not explain what the tool returns, how data is structured, or any behavioral aspects, leaving significant gaps for the agent to understand its functionality.

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 no parameter information is needed. The description does not add any parameter details, which is acceptable given the lack of inputs. This meets the baseline for tools without parameters, as it does not need to compensate for schema gaps.

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 alternatives. It does not mention context, prerequisites, or comparisons to sibling tools like '实时数据/微博热搜' or '实时数据/知乎热榜'. This leaves the agent without direction on selection among similar hot-topic tools.

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