Skip to main content
Glama
Sign In
qmcp

qmcp

by BigKAA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

qdrant_watch_start

Start watching specified file paths to trigger automatic reindexing on changes, enabling live updates for code and documentation search.

Instructions

Start watching paths for file changes and auto-reindex.

This enables live updates - files are reindexed when modified.

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

Input Schema

NameRequiredDescriptionDefault
pathsYesPaths to watch for changes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

B3.4/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 disclose the key behavior: files are reindexed automatically when modified. It says nothing about idempotency (what happens if a watcher is already running for these paths), lifetime of the watch, resource cost, or error conditions — significant gaps for a stateful background process.

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?

Short and front-loaded, leading with the action and following with its effect. The second sentence largely restates 'auto-reindex' from the first, which is mild redundancy rather than 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 and there is only one simple parameter, so return values need no explanation. However, for a stateful watcher sitting alongside qdrant_watch_ensure and qdrant_watch_stop, the definition omits the lifecycle and duplicate-start behavior an agent needs to choose correctly.

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?

Only one parameter exists and schema coverage is 100%, with the schema already describing it as 'Paths to watch for changes'. The description adds no format, path-type, or recursion semantics 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: start watching file paths, with auto-reindex as the effect. The purpose is unmistakable, though it never names the sibling it complements (qdrant_watch_stop) or contrasts with qdrant_watch_ensure, leaving differentiation to the reader.

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?

Usage is only implied by 'enables live updates' — the agent can infer this is for keeping an index fresh while files change, but there is no explicit when-to-use, no when-not-to-use, and no reference to the ensure/stop siblings that clearly bound this tool's lifecycle.

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