Skip to main content
Glama

实时数据/搜狗热榜

Access real-time trending topics and popular searches from Sogou to monitor current internet discussions and emerging topics.

Instructions

实时数据/搜狗热榜

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Generic handler executed for the tool '实时数据/搜狗热榜'. It merges user-provided arguments with the tool-specific aid and forwards the request to the xiaobenyang.com API.
    execute: async (args) => {
        // 合并用户输入 args 和工具专属 aid
        const fullArgs = {...args, aid: aid};
        return calcXiaoBenYangApi(fullArgs);
    }
  • Dynamic registration loop where the tool '实时数据/搜狗热榜' is registered if its title matches apiDesc.title from the external API response.
    for (const apiDesc of apiDescList) {
        addToolXiaoBenYangApi(apiDesc.apiId.toString(),
            apiDesc.title,
            apiDesc.description ? apiDesc.description : apiDesc.title,
            convertParamsToZ(apiDesc.params));
    }
  • Function that generates Zod schema for tool input parameters based on Java type descriptions from the external API.
    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 performs the actual API call to xiaobenyang.com/api using the tool's aid and arguments. This implements the core logic for all tools including '实时数据/搜狗热榜'.
    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();
    }
  • Helper function that registers each individual tool with name, description, parameters, and the shared handler.
    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);
            }
        });
    }
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must fully disclose behavioral traits. However, it reveals nothing about the tool's behavior—such as whether it's read-only or destructive, its rate limits, authentication needs, or output format. This leaves the agent with no understanding of how the tool operates beyond its name.

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 concise with a single phrase, the description is under-specified rather than efficiently informative. It fails to front-load essential information and doesn't use its brevity to convey value. Every sentence should earn its place, but here the phrase adds no clarity beyond the tool name, wasting the opportunity for meaningful content.

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 '实时数据' (real-time data) and the lack of annotations or output schema, the description is incomplete. It doesn't explain what data is returned, how it's structured, or any operational constraints. For a tool likely involving dynamic data retrieval, this minimal description is inadequate for effective agent 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, 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. A baseline score of 4 is appropriate as there are no parameters to explain, and the description doesn't introduce any confusion about inputs.

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 offers no guidance on when to use this tool versus alternatives. It doesn't mention any context, prerequisites, or exclusions, nor does it reference sibling tools. Without any usage instructions, an agent cannot determine appropriate scenarios for invoking this tool over others in the list.

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