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_store

DestructiveIdempotent

Delete a Cognigy.AI knowledge store and all its sources and chunks. Set dryRun=false to confirm permanent removal.

Instructions

Deletes a Cognigy.AI knowledge store and ALL its sources and chunks. WARNING: This is destructive and cannot be undone. AI Agents using this store will lose access. 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": {
      "knowledgeStoreId": "<knowledgeStoreId>"
    },
    "name": "delete_knowledge_store"
  }
}

Input Schema

NameRequiredDescriptionDefault
dryRunNoIf true (default), validates without deleting. Set to false to actually delete.
knowledgeStoreIdYesThe knowledge store ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A4.6/5.0
Behavior5/5

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

Discloses destructive behavior, irreversible impact, and loss of access for AI Agents, going beyond annotations. Adds context about cascading deletion of sources and chunks, which is not in annotations or schema.

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?

Description is short (3 sentences) with clear front-loading of action, then warning, then instruction. No redundant or irrelevant information.

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?

Covers the essential details: action, scope, impact, and safety mechanism. Lacks mention of required permissions or return behavior, but no output schema is expected and the tool is straightforward.

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?

Input schema has 100% parameter description coverage, so baseline is 3. Description adds value by clarifying dryRun usage and mutating nature, providing context beyond the schema.

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?

Explicitly states it deletes a knowledge store and all its sources/chunks, using a specific verb and resource. Clearly distinguishes from sibling tools like delete_knowledge_source and delete_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?

Provides warning about destructive nature and mentions dryRun parameter for safe validation. However, lacks explicit guidance on when to use this tool versus other deletion tools, and does not state prerequisites or alternative approaches.

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