Skip to main content
Glama

request_baike

Fetch and render Baidu Baike article discussions to access Chinese encyclopedia content and generate readable analysis from structured data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes百度百科URL,例如:https://baike.baidu.com/item/DeepSeek

Implementation Reference

  • The main handler function for the "request_baike" tool. It takes a Baidu Baike URL, fetches discussions using BaikeClient, and returns the JSON-formatted discussions as text content or an error message.
    async ({ url }: { url: string }) => {
      try {
        const discussions = await baikeClient.getDiscussions(url);
        
        return {
          content: [
            { 
              type: "text", 
              text: JSON.stringify(discussions, null, 2)
            }
          ]
        };
      } catch (error) {
        const errorMessage = error instanceof Error 
          ? error.message 
          : "获取百科讨论时发生未知错误";
        
        return {
          content: [{ type: "text", text: errorMessage }],
          isError: true
        };
      }
    }
  • Input schema definition for the "request_baike" tool using Zod, requiring a single 'url' parameter of type string.
    { url: z.string().describe("百度百科URL,例如:https://baike.baidu.com/item/DeepSeek") },
  • src/index.ts:29-55 (registration)
    MCP server tool registration for "request_baike", including the tool name, input schema, and handler function.
    server.tool(
      "request_baike",
      { url: z.string().describe("百度百科URL,例如:https://baike.baidu.com/item/DeepSeek") },
      async ({ url }: { url: string }) => {
        try {
          const discussions = await baikeClient.getDiscussions(url);
          
          return {
            content: [
              { 
                type: "text", 
                text: JSON.stringify(discussions, null, 2)
              }
            ]
          };
        } catch (error) {
          const errorMessage = error instanceof Error 
            ? error.message 
            : "获取百科讨论时发生未知错误";
          
          return {
            content: [{ type: "text", text: errorMessage }],
            isError: true
          };
        }
      }
    );
  • BaikeClient.getDiscussions helper method: parses URL to lemmaId, makes API request to fetch Baike discussions, handles errors.
    async getDiscussions(lemmaIdOrUrl: string): Promise<BaikeDiscussionResponse> {
      const lemmaId = this.parseLemmaIdOrUrl(lemmaIdOrUrl);
      
      try {
        const response = await axios.get<BaikeDiscussionResponse>(
          `${this.apiBaseUrl}${this.discussionApiPath}?lemmaId=${lemmaId}`,
          {
            headers: {
              "Content-Type": "application/json",
              cookie: this.cookie,
            },
          }
        );
        
        return response.data;
      } catch (error: unknown) {
        if (axios.isAxiosError(error) && error.response) {
          throw new Error(`百度百科API错误: ${error.response.status} - ${JSON.stringify(error.response.data)}`);
        }
        throw error;
      }
    }
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no 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?

Tool has no description.

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?

Tool has no description.

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/Zzzccs123/mcp-baike-render'

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