Skip to main content
Glama
Sign In
@asyntai/mcp

@asyntai/mcp

Official
by asyntai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Delete a knowledge base entry

delete_knowledge_entry
DestructiveIdempotent

Permanently remove a knowledge base entry and all its associated passages. The chatbot instantly stops using that content. This action cannot be undone.

Instructions

Permanently delete one knowledge base entry and every passage built from it. The chatbot stops using that content immediately. This cannot be undone.

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": {
      "entry_id": "<entry_id>"
    },
    "name": "delete_knowledge_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
entry_idYesThe entry id from list_knowledge.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A5/5.0
Behavior5/5

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

Description explicitly states permanence ('cannot be undone') and cascading deletion ('every passage built from it'), which aligns with and enriches the destructiveHint and idempotentHint annotations without contradiction.

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 two concise sentences covering all essential information without redundancy or irrelevant details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Fully covers the scope of deletion, permanence, effect on the chatbot, and source of the id, making the operation complete and unambiguous for the agent.

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

Parameters5/5

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

The single parameter entry_id is clearly described as coming from list_knowledge, providing sufficient context for the expected value even beyond the schema's own description.

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?

Clearly states the action (permanently delete), the resource (knowledge base entry and its passages), and distinguishes from sibling tools that add or list knowledge.

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

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance that the chatbot stops using the content immediately and indicates the entry id comes from list_knowledge, which gives the user a clear path to invoke correctly.

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

Deploy Server

Other Tools