Skip to main content
Glama

实时数据/B站热榜

Get real-time Bilibili trending rankings to monitor popular content and track video performance on the platform.

Instructions

实时数据/B站热榜

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function that executes the tool logic for all dynamically loaded tools, including "实时数据/B站热榜". 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();
    }
  • Converts Java parameter descriptions from the external API into Zod schema for input validation of tools like "实时数据/B站热榜".
    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);
    }
  • Dynamically registers all tools, including "实时数据/B站热榜", by iterating over apiDescList fetched from the external API and adding them via server.addTool with title as the tool name.
    for (const apiDesc of apiDescList) {
        addToolXiaoBenYangApi(apiDesc.apiId.toString(),
            apiDesc.title,
            apiDesc.description ? apiDesc.description : apiDesc.title,
            convertParamsToZ(apiDesc.params));
    }
  • Helper function that registers a single tool on the FastMCP server, binding the specific aid to the generic handler. Used for each tool including "实时数据/B站热榜".
    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);
            }
        });
    }
  • Helper that converts Java type strings (with generics) to Zod schemas, used in parameter schema generation for all tools.
    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({});
    }

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
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 behaviorally - whether it fetches, displays, filters, or processes the Bilibili hot list data. It doesn't indicate if this is a read operation, whether it requires authentication, what format the data comes in, or any other behavioral characteristics.

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 (just the tool name repeated), this is under-specification rather than effective conciseness. The description doesn't communicate any useful information in its minimal form. A truly concise description would still convey the tool's purpose and basic operation, which this completely fails to do.

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 tool's apparent purpose (fetching Bilibili hot list data), the lack of annotations, no output schema, and the presence of many similar sibling tools, this description is completely inadequate. It provides no information about what the tool returns, how it behaves, or how it differs from alternatives. For a data-fetching tool in a crowded namespace, this minimal description fails to provide the necessary 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 zero parameters, and the schema description coverage is 100% (though with no parameters, this is trivial). The description doesn't need to explain parameters since there are none. However, it also doesn't mention that this is a parameterless tool, which could be slightly helpful context. Given the zero-parameter baseline, this earns a 4 rather than a perfect 5.

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 absolutely no guidance about when to use this tool versus its many alternatives. With 15 sibling tools that all appear to provide hot lists from different platforms (微博热搜, 抖音热榜, 知乎热榜, etc.), the agent has no information about why one would choose the Bilibili hot list over any other platform's hot list. There's no context about use cases, prerequisites, or differentiation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.