Skip to main content
Glama
Sign In
qmcp

qmcp

by BigKAA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

qdrant_delete_collection

Deletes a specified Qdrant collection to remove its stored vectors and associated indexing data, helping clear unused or obsolete datasets.

Instructions

Delete a collection from Qdrant.

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

Input Schema

NameRequiredDescriptionDefault
nameYesCollection name to delete

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and largely fails it. It never states that deletion destroys all points and indexes permanently, whether the operation requires elevated permissions, or whether it fails when the collection is missing. For an irreversible operation, that is a substantial omission.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero waste, which is appropriate for a one-parameter tool. It is arguably too terse given the destructive nature, but no sentence is superfluous.

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

Completeness2/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-value explanation is unnecessary, and the single parameter is fully described. However, for an irreversible deletion with no annotations, the definition should warn about data loss and confirm the target scope; that critical context is absent.

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 100% and the single parameter 'name' is already documented as the collection name to delete. The description adds no format constraints, naming rules, or error behavior beyond the schema, so the baseline of 3 applies.

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: 'Delete a collection from Qdrant.' An agent can immediately tell this removes a whole collection rather than records or indexes, distinguishing it from siblings like qdrant_cleanup or qdrant_reindex. It does not explicitly name those alternatives, keeping it below a 5.

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 when-to-use or when-not-to-use guidance, no mention that this is irreversible, and no pointer to safer inspection siblings such as qdrant_get_collection_info or qdrant_list_collections. The agent must infer that this is the destructive option from the verb alone.

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