Skip to main content
Glama
VinayakTiwari1103

MCP-Smallest.ai

createKnowledgeBase

Create structured knowledge bases by defining names and descriptions, enabling organized information management within the MCP-Smallest.ai server system.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionYes
nameYes

Implementation Reference

  • index.ts:50-77 (handler)
    The handler function that implements the createKnowledgeBase tool. It makes a POST request to the /knowledgebase endpoint with the provided name and description, returns the JSON response or an error.
    async (args) => {
      try {
        const response = await fetch(`${config.BASE_URL}/knowledgebase`, {
          method: 'POST',
          headers: {
            'Authorization': `Bearer ${config.API_KEY}`,
            'Content-Type': 'application/json'
          },
          body: JSON.stringify({ name: args.name, description: args.description })
        });
    
        if (!response.ok) {
          throw new Error(`HTTP error! status: ${response.status}`);
        }
    
        const data = await response.json();
        return {
          content: [{ type: "text", text: JSON.stringify(data, null, 2) }]
        };
      } catch (error: unknown) {
        const errorMessage = error instanceof Error ? error.message : 'Unknown error occurred';
        console.error('Error creating knowledge base:', error);
        return {
          content: [{ type: "text", text: `Error: ${errorMessage}` }],
          isError: true
        };
      }
    }
  • Zod schema defining the input parameters for the createKnowledgeBase tool: name (string) and description (string).
    {
      name: z.string(),
      description: z.string()
    },
  • index.ts:44-78 (registration)
    The server.tool() call that registers the createKnowledgeBase tool with its schema and handler function.
    server.tool(
      "createKnowledgeBase",
      {
        name: z.string(),
        description: z.string()
      },
      async (args) => {
        try {
          const response = await fetch(`${config.BASE_URL}/knowledgebase`, {
            method: 'POST',
            headers: {
              'Authorization': `Bearer ${config.API_KEY}`,
              'Content-Type': 'application/json'
            },
            body: JSON.stringify({ name: args.name, description: args.description })
          });
    
          if (!response.ok) {
            throw new Error(`HTTP error! status: ${response.status}`);
          }
    
          const data = await response.json();
          return {
            content: [{ type: "text", text: JSON.stringify(data, null, 2) }]
          };
        } catch (error: unknown) {
          const errorMessage = error instanceof Error ? error.message : 'Unknown error occurred';
          console.error('Error creating knowledge base:', error);
          return {
            content: [{ type: "text", text: `Error: ${errorMessage}` }],
            isError: true
          };
        }
      }
    );
  • config.ts:1-4 (helper)
    Configuration module providing API_KEY and BASE_URL constants used by the createKnowledgeBase handler for authentication and endpoint.
    export const config = {
        API_KEY: 'smallest-ai-api-key',
        BASE_URL: 'https://atoms-api.smallest.ai/api/v1'
    }; 
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

Related 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/VinayakTiwari1103/MCP-smallest-ai'

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