Skip to main content
Glama
Sign In
qmcp

qmcp

by BigKAA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

qdrant_diagnose_collection

Run full diagnostics on a Qdrant collection to analyze vector counts, file and chunk type distribution, indexing date ranges, and detect issues like missing hashes or empty chunks.

Instructions

Perform full diagnostics of a collection.

Analyzes the collection and returns:
- Total vectors and files count
- File type distribution
- Chunk type distribution
- Indexing timestamp range (oldest/newest)
- Issues found (missing hashes, empty chunks, etc.)
- List of all indexed files with details

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

Input Schema

NameRequiredDescriptionDefault
collectionYesCollection name to diagnose

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 provided, so the description carries the full burden. It implies a read-only analysis ('Analyzes the collection and returns') and usefully signals a potentially heavy, wide output ('List of all indexed files with details'), but it never explicitly states that nothing is mutated, whether the scan is expensive on large collections, or whether it requires special access.

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?

One front-loaded purpose sentence followed by a scannable bullet list; nothing is padded. The bullets partially duplicate the existing output schema, which is the only mild waste.

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 the return-value enumeration is arguably redundant, and with one required parameter the surface is simple. However, with zero annotations the description should compensate by stating that the operation is non-destructive and what to expect on large collections, which it does not.

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?

There is a single parameter with 100% schema description coverage ('Collection name to diagnose'), so the schema already does the work. The description adds no format, naming convention, or error-case detail beyond that baseline.

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?

The description opens with a specific verb and resource ('Perform full diagnostics of a collection') and enumerates the exact report contents, which lets an agent distinguish it from simpler siblings like qdrant_get_collection_info or qdrant_list_indexed_files. It stops short of naming those siblings explicitly.

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?

Diagnostic intent is implied by the word 'diagnostics' and the issue-reporting bullets, but there is no explicit statement of when to reach for this tool versus qdrant_get_collection_info, qdrant_list_indexed_files, or qdrant_diff_collection, and no exclusions or prerequisites are stated.

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