Skip to main content
Glama
ragflow-kb-mcp
by feci

ragflow_delete_chat

Destructive

Permanently delete a chat assistant and all its sessions by chat ID to remove obsolete assistants and associated session data.

Instructions

Permanently delete one chat assistant and its sessions.

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": {
      "chat_id": "<chat_id>"
    },
    "name": "ragflow_delete_chat"
  }
}

Input Schema

NameRequiredDescriptionDefault
chat_idYesChat assistant ID

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description still adds real value by disclosing the cascade effect ('and its sessions'), which is not encoded in the annotations and is the key thing an agent needs to know before invoking it. Missing only prerequisite/permission details.

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?

One short sentence, front-loaded with the destructive verb and with no filler. Every phrase ('Permanently', 'one', 'and its sessions') carries 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?

Output schema exists, so return values need not be described, and annotations cover the safety profile. The description covers destructive scope and cascade deletion, which is the essential remaining gap for a single-parameter delete, though permission requirements and recovery options are unaddressed.

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?

Single parameter chat_id with 100% schema description coverage, so the schema already carries parameter documentation. The phrase 'one chat assistant' reinforces that this takes a single ID rather than a list, but adds no format or validation detail beyond the schema pattern.

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

Purpose4/5

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

States a specific verb and resource ('Permanently delete one chat assistant') plus the cascade scope ('and its sessions'). 'One' implicitly contrasts with the bulk sibling ragflow_delete_chats, but that alternative is never named, so differentiation is inferred rather than stated.

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

Usage Guidelines3/5

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

Usage is only implied by the name and the word 'Permanently'. There is no explicit when-to-use guidance, no mention of the bulk sibling ragflow_delete_chats or ragflow_delete_chat_sessions, and no prerequisites such as required permissions or confirmation steps.

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