Skip to main content
Glama
Sign In
qmcp

qmcp

by BigKAA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

qdrant_watch_ensure

Ensures the watcher is active for the current workspace without dropping other projects by merging requested, configured, and existing paths, and restarts only when the watch set changes.

Instructions

Ensure watcher is active for the current workspace without dropping other projects.

This tool is designed for OpenCode sessions where one global MCP server is shared across multiple repositories. It merges workspace paths with the configured and/or currently watched paths and only restarts the watcher when the effective watch set changes.

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

Input Schema

NameRequiredDescriptionDefault
pathsYesWorkspace paths that must be watched
include_existingNoKeep paths that are already being watched by the running server
include_configuredNoKeep paths configured through WATCH_PATHS on server startup

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses that paths are merged with configured and currently-watched paths, that other projects are preserved, and that a restart happens only when the effective watch set changes. It omits what happens if no watcher is running (implicitly started?) and any error/failure behavior, leaving a gap for a stateful server operation.

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?

The core action and its safety property are front-loaded in the first sentence, and the second sentence supplies the scenario that justifies the tool. Three sentences, minimal waste, though the OpenCode-specific framing could be trimmed slightly for general readers.

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?

An output schema exists, so return values need no explanation, and all three parameters are documented in both schema and description. The remaining gap is failure/edge behavior (watcher not running, invalid path, restart cost), which matters for a tool that mutates server state.

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 the baseline is 3; the description earns an extra point by explaining the merge semantics that give meaning to include_existing and include_configured ('merges workspace paths with the configured and/or currently watched paths') rather than just restating them.

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 leads with a specific verb and resource ('Ensure watcher is active for the current workspace') plus the key qualifier 'without dropping other projects'. It implicitly separates itself from a naive start/restart by describing merge semantics, though it never names qdrant_watch_start or qdrant_watch_stop explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the usage context clearly: 'designed for OpenCode sessions where one global MCP server is shared across multiple repositories', which tells an agent when this tool is the right pick. It does not spell out when-not conditions or point to the sibling start/stop tools for the single-repo case.

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