Skip to main content
Glama
Sign In
qmcp

qmcp

by BigKAA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

qdrant_reindex

Reindex a directory for semantic search by fully rebuilding its Qdrant collection or updating only changed files.

Instructions

Reindex a directory - either full rebuild or incremental update.

Full mode deletes the collection and recreates it from scratch. Incremental mode only updates changed files.

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": {
      "path": "<path>",
      "collection": "<collection>"
    },
    "name": "qdrant_reindex"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoReindex mode: 'full' or 'incremental'incremental
pathYesDirectory path to reindex
collectionYesCollection name to reindex

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does make one genuinely valuable disclosure: full mode destroys and recreates the collection. Beyond that, nothing is said about whether the collection must already exist, whether incremental is safe/non-destructive, permission requirements, or cost of a full rebuild.

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?

Three short, front-loaded sentences with no filler; the destructive consequence of full mode is stated immediately after the mode is named, which is exactly where an agent needs it.

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

Completeness3/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 described. However, this is a mutating tool with zero annotation coverage whose description omits prerequisites (must the collection exist?), irreversibility of the full rebuild, and scope of impact, leaving meaningful gaps for a destructive operation.

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?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning by explaining what each mode value does operationally rather than just listing "'full' or 'incremental'" as the schema does. Path and collection remain purely schema-documented.

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?

Uses a specific verb+resource ("Reindex a directory") and distinguishes the two operating modes. It does not, however, differentiate itself from the sibling qdrant_index_directory, leaving the agent to infer which entry point to use.

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?

"Full mode deletes the collection and recreates it" versus "Incremental mode only updates changed files" effectively tells the agent how to choose a mode, but there is no guidance on when to use this tool at all versus qdrant_index_directory, qdrant_delete_collection, or qdrant_cleanup.

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