lore-mcp

kb_delete

Remove an existing knowledge base entry from the database by providing its unique ID.

Instructions

Delete existing KB entry from database

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "kb_id": "<kb_id>"
    },
    "name": "kb_delete"
  }
}

Input Schema

Name	Required	Description	Default
`kb_id`	Yes
`confirm`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.8.5May 28, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
removedInput schema / properties / confirm / description
```
Removed value: -"Confirmation flag for safety"
```
removedInput schema / properties / kb_id / description
```
Removed value: -"kb_id of entry to delete"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object",
+  "x-fastmcp-wrap-result": true
+}

Changed3 schema fields changedv0.8.2May 27, 2026

removedInput schema / properties / entry_id

Removed value: -{
-  "description": "UUID of entry to delete",
-  "type": "string"
-}

addedInput schema / properties / kb_id

Added value: +{
+  "description": "kb_id of entry to delete",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "entry_id"
-]New value: +[
+  "kb_id"
+]

First observedv0.7.0May 25, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Despite no annotations, the description merely repeats the action without disclosing behavioral traits like destructive nature, the need for confirmation, or side effects. It adds little beyond the tool name.

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

Conciseness3/5

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

One sentence with no redundancy, but extremely minimal. It is concise at the expense of necessary detail.

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 tool's destructive nature and the confirm parameter, the description lacks essential context such as the permanence of deletion and the role of confirm. The output schema exists but does not compensate for the missing behavioral context.

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?

Schema description coverage is 0%, and the description provides no information about parameters (kb_id, confirm) beyond what the schema defines. This is a critical gap.

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

Purpose5/5

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

The description clearly states the action ('Delete') and the resource ('existing KB entry from database'), distinguishing it from sibling tools like kb_add (create) and kb_update (modify).

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 on when to use this tool versus alternatives, no mention of irreversibility or prerequisites. Only implied usage from the name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.