Skip to main content
Glama
Datris MCP Server

Datris MCP Server

search_qdrant

Perform semantic search across a Qdrant vector database collection by converting natural language queries into embeddings and returning similar document chunks with similarity scores for RAG workflows.

Instructions

Semantic search across a Qdrant vector database collection. Takes a natural language query, generates an embedding, and returns the most similar document chunks with similarity scores. For RAG: pass the returned text to ai_answer with the user's question.

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": {
      "query": "<query>"
    },
    "name": "search_qdrant"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesNatural language search query
top_kNoNumber of results to return (default: 5)
collectionNoQdrant collection name (default: documents)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the burden, and it does disclose the key behavior: a query is embedded and results come back as document chunks ranked by similarity score, which implies embedding cost/latency. It omits error behavior (e.g., missing collection) and any permission or rate-limit context, which for a read-only search is a modest gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with what the tool does, then the return shape, then the follow-up action. Nothing is redundant with the schema and no sentence is filler.

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?

There is no output schema, and the description compensates by describing the returned value as ranked document chunks with similarity scores. For a three-parameter read tool that is largely sufficient, though a note on collection defaults or failure modes would close the remaining gap.

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 query, top_k, and collection are already documented with defaults. The description adds no syntax, format, or tuning guidance beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Semantic search across a Qdrant vector database collection') and names the mechanism (embedding generation, similar chunks with similarity scores). The provider name Qdrant plus the explicit ai_answer handoff separates it from the sibling vector-store search tools.

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?

The 'For RAG: pass the returned text to ai_answer' sentence gives concrete context for when and how to use the results, which is the main usage decision an agent faces. It stops short of naming when NOT to use this tool or pointing to sibling alternatives such as search_chroma for non-Qdrant data.

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