Skip to main content
Glama
Sign In
qmcp

qmcp

by BigKAA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

qdrant_cleanup

Remove stale vectors for deleted or changed files by comparing a Qdrant collection against the indexed repository path, with an optional dry run to preview deletions.

Instructions

Clean up stale vectors - remove vectors for deleted or 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": {
      "collection": "<collection>",
      "repo_path": "<repo_path>"
    },
    "name": "qdrant_cleanup"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNoIf True, only report what would be deleted
repo_pathYesRepository path to compare against (directory that was indexed)
collectionYesCollection name to clean

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the deletion scope ('vectors for deleted or changed files'), which is real behavioral value, but it omits irreversibility, required permissions, and the existence of a safe dry-run default that lives only in the schema. For a destructive operation with zero annotation coverage, this is a notable gap.

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 compact sentence with the action front-loaded and no filler. It is efficient, though it pays for that brevity with the missing usage and safety context noted above.

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 and all parameters are documented, so the structural side is covered. However, for a destructive maintenance operation with no annotations, the description should say more about safety and when to invoke it; it is adequate but incomplete.

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%, so all three parameters including dry_run's default and meaning are already documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline 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: 'Clean up stale vectors - remove vectors for deleted or changed files.' The agent can tell this deletes orphaned vectors, which is meaningfully different from read-only siblings like qdrant_get_collection_info or qdrant_diff_collection. It does not explicitly name a sibling to differentiate from (e.g., qdrant_reindex or qdrant_diff_collection), so it falls short of 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?

The description never says when to run this versus alternatives such as qdrant_diff_collection or qdrant_reindex, nor when not to run it. The only guidance is implied by 'stale vectors,' leaving the agent to infer the workflow context itself.

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