Skip to main content
Glama
Sign In
qmcp

qmcp

by BigKAA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

qdrant_list_indexed_files

List indexed files in a Qdrant collection with pagination and filtering by file type, returning paths, chunk counts, hashes, timestamps, and chunk types.

Instructions

List all indexed files in a collection with pagination.

Returns file metadata including:
- File path
- Number of chunks
- Content hash
- Indexed timestamp
- Chunk types found in file

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_list_indexed_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax files to return
offsetNoPagination offset
file_typeNoFilter by file extension (e.g., '.py', '.go')
collectionYesCollection name

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 behavioral burden. 'List' correctly signals a read-only operation and pagination behavior is noted, but nothing covers ordering of results, behavior on a missing/empty collection, or cost on very large collections. The returned-field list is helpful framing but largely duplicates the output schema.

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?

Two tight parts: a front-loaded purpose sentence followed by a short bulleted list. The bullets restate return fields already present in the output schema, which is mild redundancy, but the overall length and ordering are appropriate.

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?

This is a simple read-only list tool with a full-coverage input schema and an output schema, so almost everything an agent needs is already structured. The description is complete for correct invocation; only the when-to-use dimension is left unaddressed.

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 each of the four parameters (collection, limit, offset, file_type) is documented in the schema itself. The description adds only the general notion of pagination; it does not explain limit/offset interaction or file_type filtering beyond what the schema states, 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?

The description opens with a specific verb and resource: 'List all indexed files in a collection with pagination.' That is clearly distinct from qdrant_list_collections (which lists collections) and qdrant_index_directory (which writes). It does not explicitly name a sibling to contrast with, which keeps it just 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?

There is no guidance on when to call this instead of qdrant_get_collection_info, qdrant_diff_collection, or qdrant_search. The word 'pagination' hints at large collections but nothing states a selection condition or prerequisite (e.g., that the collection must already be indexed).

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