Skip to main content
Glama
dannwaneri

MCP Knowledge Base Server

by dannwaneri

list_categories

Retrieve all available knowledge base categories to organize and filter content for efficient information access.

Instructions

List all available knowledge base categories

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the 'list_categories' tool. Extracts unique categories from the global knowledgeBase array using Set, formats them into a JSON response with count, caches the result, and returns it as text content.
    if (name === "list_categories") {
      const categories = [...new Set(knowledgeBase.map((item) => item.category))];
    
      const responseText = JSON.stringify(
        {
          categories,
          count: categories.length,
        },
        null,
        2
      );
    
      // Cache the response
      setCache(cacheKey, responseText);
    
      return {
        content: [
          {
            type: "text",
            text: responseText,
          },
        ],
      };
    }
  • src/index.ts:156-163 (registration)
    Registration of the 'list_categories' tool in the listTools response, including name, description, and empty input schema (no parameters required).
    {
      name: "list_categories",
      description: "List all available knowledge base categories",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Input schema for 'list_categories' tool: an empty object, indicating no input parameters are needed.
    inputSchema: {
      type: "object",
      properties: {},
    },
Behavior2/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. It states the action ('List all available') but doesn't describe key traits like whether it's read-only, if it requires authentication, rate limits, pagination, or what the return format looks like. For a tool with zero annotation coverage, this is a significant gap in transparency.

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

Conciseness5/5

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

The description is a single, efficient sentence that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain behavioral aspects like safety, performance, or return values, which are crucial for an agent to use the tool effectively. For a tool with no structured data beyond the input schema, the description should provide more 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 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately avoids unnecessary details, earning a baseline score of 4 for this dimension.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('List') and resource ('knowledge base categories'), making the purpose specific and understandable. However, it doesn't differentiate from sibling tools like 'get_by_category' or 'search_knowledge', which might also involve categories, so it's not fully distinguished from alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/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 such as 'advanced_search' or 'get_by_category'. It lacks context about use cases, prerequisites, or exclusions, leaving the agent to infer usage from the tool name alone.

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/dannwaneri/mcp-knowledge-base-server'

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