Skip to main content
Glama
Sign In
cognigy-ai-mcp-management-server

cognigy-ai-mcp-management-server

by TsvetanG2
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript

delete_knowledge_chunk

DestructiveIdempotent

Validate and delete a knowledge chunk from a store. Set dryRun to false to permanently remove and stop RAG search.

Instructions

Deletes a Cognigy.AI knowledge chunk. The content will no longer be searchable via RAG. MUTATING: Set dryRun=false to delete.

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": {
      "chunkId": "<chunkId>",
      "sourceId": "<sourceId>",
      "knowledgeStoreId": "<knowledgeStoreId>"
    },
    "name": "delete_knowledge_chunk"
  }
}

Input Schema

NameRequiredDescriptionDefault
dryRunNoIf true (default), validates without deleting. Set to false to actually delete.
chunkIdYesThe knowledge chunk ID to delete
sourceIdYesThe knowledge source ID containing the chunk
knowledgeStoreIdYesThe knowledge store ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds context about the content becoming unsearchable via RAG, going beyond what annotations provide. No contradictions.

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 sentences, front-loading the purpose and adding a practical usage note. Every sentence is meaningful and efficient.

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

Completeness4/5

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

For a simple deletion tool with no output schema, the description covers the key behavioral impact (RAG searchability) and the dryRun safeguard. A note on the return value would be slightly more complete, but not essential.

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

Parameters3/5

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

Schema coverage is 100%, and the description does not add any additional parameter meaning beyond what is already in the schema. The mention of dryRun is redundant with the schema 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?

The description clearly states 'Deletes a Cognigy.AI knowledge chunk' with a specific verb and resource, distinguishing it from sibling tools like get/update_knowledge_chunk.

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

Usage Guidelines4/5

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

The description advises 'Set dryRun=false to delete,' providing a clear usage guideline. It implies when not to perform the actual deletion (dryRun=true). No explicit alternatives are mentioned, but the context is clear.

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