Skip to main content
Glama
io.github.avaazquezz/mcp-qdrant

io.github.avaazquezz/mcp-qdrant

by avaazquezz

Delete Qdrant collection

qdrant_collection_delete
DestructiveIdempotent

Delete a Qdrant collection and all its points in one call, returning without error when the collection does not exist.

Instructions

Delete a collection and all its points; a no-op if it doesn't exist.

    Example: {"collection_name": "docs"}
    

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": {
      "collection_name": "<collection_name>"
    },
    "name": "qdrant_collection_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
collection_nameYes

Output Schema

NameRequiredDescriptionDefault
deletedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description still adds real value by disclosing cascade behavior — deleting a collection also removes all of its points — and restating no-op-on-absence in plain language.

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?

Two short units: the behavior sentence first, then a compact call example. Every line earns its place and the most important fact (cascading deletion) is front-loaded.

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?

An output schema exists, so return values need not be explained, and there is only one parameter. For a destructive operation, a short warning to confirm the collection name or check existence would round it out, but nothing an agent needs to invoke it is missing.

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 description coverage is 0% and the single parameter has no documentation in the schema, so the description carries the burden. It only supplies a minimal example ({"collection_name": "docs"}), which implies the value is a plain name string but says nothing about naming rules, sources for valid names, or default behavior.

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+resource ("Delete a collection") and adds scope ("and all its points"), which lets an agent distinguish it from qdrant_points_delete. It never names a sibling explicitly, but the resource noun does the differentiation work.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus qdrant_points_delete or qdrant_collection_update, and no suggested prerequisite such as checking qdrant_collection_exists/list first. The only contextual note ("a no-op if it doesn't exist") is behavioral, not usage-routing.

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