Skip to main content
Glama

delete_document

Remove a document and its chunks from the knowledge base after updates or when no longer needed.

Instructions

Remove a document and all its chunks from the knowledge base.

This is useful when a document has been updated (you'll delete then re-index it) or when you no longer need it to be searchable.

Args: source: The filename of the document to remove, e.g. "design_doc.pdf". Use list_indexed_docs to see valid filenames.

Returns: Confirmation message with the number of chunks deleted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations, but description clearly indicates destructive behavior and return confirmation. Could mention permanence, but adequate.

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?

Concise docstring format with no fluff; every sentence adds value.

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?

Complete for a simple delete tool with one param and output schema mentioned.

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?

Describes 'source' parameter with example and reference to list_indexed_docs for valid values, adding value beyond 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?

Clearly states 'Remove a document and all its chunks from the knowledge base.' Distinguishes from sibling tools (index, list, search).

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?

Explicitly says when to use: after update or when no longer needed. References list_indexed_docs for valid filenames.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Kamalesh-Kavin/rag-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server