Skip to main content
Glama

kb_remove_custom

Delete specific custom knowledge entries from persistent storage by specifying category and key to manage stored information.

Instructions

Remove custom knowledge

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryYes
keyYes

Implementation Reference

  • src/index.ts:179-190 (registration)
    Tool registration including name, description, and input schema for kb_remove_custom.
    {
      name: 'kb_remove_custom',
      description: 'Remove custom knowledge',
      inputSchema: {
        type: 'object',
        properties: {
          category: { type: 'string' },
          key: { type: 'string' }
        },
        required: ['category', 'key']
      }
    },
  • MCP tool handler that delegates to KnowledgeManager.removeCustomKnowledge and formats response.
    case 'kb_remove_custom': {
      const { category, key } = args as any;
      const removed = await km.removeCustomKnowledge(category, key);
      return {
        content: [
          {
            type: 'text',
            text: removed 
              ? `✅ Removed custom knowledge: ${category}/${key}`
              : `❌ Not found: ${category}/${key}`
          }
        ]
      };
    }
  • Core implementation in KnowledgeManager that removes the specified custom knowledge entry, logs to history, persists changes, and returns success status.
    async removeCustomKnowledge(category: string, key: string): Promise<boolean> {
      const index = this.kb.custom.findIndex(k => k.category === category && k.key === key);
      if (index >= 0) {
        const oldValue = this.kb.custom[index].value;
        this.kb.custom.splice(index, 1);
        this.addHistory({
          action: 'delete',
          category: `custom:${category}`,
          field: key,
          oldValue
        });
        await this.save();
        return true;
      }
      return false;
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'Remove' implies a destructive mutation, but it doesn't disclose if this is permanent, requires specific permissions, affects related data, or has side effects. For a deletion tool with zero annotation coverage, this is a significant gap in behavioral context.

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 phrase with no wasted words. It's appropriately sized for a simple tool name and front-loaded with the core action, though this brevity contributes to gaps in other dimensions.

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 complexity of a deletion operation, no annotations, no output schema, and 0% schema coverage, the description is incomplete. It doesn't explain what 'custom knowledge' is, how removal works, what happens on success/failure, or return values, making it inadequate for safe and effective use.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It mentions 'custom knowledge' but doesn't explain what 'category' and 'key' parameters represent, their formats, or examples. Without this, the schema's two required parameters remain undocumented, leaving the agent guessing about their meaning.

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

Purpose3/5

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

The description 'Remove custom knowledge' states the action (remove) and resource (custom knowledge), but is vague about what 'custom knowledge' refers to and doesn't differentiate from sibling tools like kb_get_custom or kb_update_*. It's better than a tautology but lacks specificity about the scope of removal.

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like kb_get_custom (retrieve), kb_update_* (modify), and kb_export/import (manage data), the description offers no context for choosing removal over other operations or prerequisites for deletion.

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/hlsitechio/mcp-instruct'

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