Skip to main content
Glama
qdrant

mcp-server-qdrant

Official
by qdrant

qdrant-find

Search for memories by content in Qdrant vector databases to retrieve stored information for analysis or personal data access.

Instructions

Look up memories in Qdrant. Use this tool when you need to:

  • Find memories by their content

  • Access memories for further analysis

  • Get some personal information about the user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesWhat to search for
collection_nameYesThe collection to search in

Implementation Reference

  • Core handler function 'find' implementing qdrant-find tool: processes query and filter, searches Qdrant collection, formats results into a list of strings.
    async def find(
        ctx: Context,
        query: Annotated[str, Field(description="What to search for")],
        collection_name: Annotated[
            str, Field(description="The collection to search in")
        ],
        query_filter: ArbitraryFilter | None = None,
    ) -> list[str] | None:
        """
        Find memories in Qdrant.
        :param ctx: The context for the request.
        :param query: The query to use for the search.
        :param collection_name: The name of the collection to search in, optional. If not provided,
                                the default collection is used.
        :param query_filter: The filter to apply to the query.
        :return: A list of entries found or None.
        """
    
        # Log query_filter
        await ctx.debug(f"Query filter: {query_filter}")
    
        query_filter = models.Filter(**query_filter) if query_filter else None
    
        await ctx.debug(f"Finding results for query {query}")
    
        entries = await self.qdrant_connector.search(
            query,
            collection_name=collection_name,
            limit=self.qdrant_settings.search_limit,
            query_filter=query_filter,
        )
        if not entries:
            return None
        content = [
            f"Results for the query '{query}'",
        ]
        for entry in entries:
            content.append(self.format_entry(entry))
        return content
  • Tool registration for 'qdrant-find' using the wrapped 'find_foo' function.
    self.tool(
        find_foo,
        name="qdrant-find",
        description=self.tool_settings.tool_find_description,
    )
  • Input schema defined via Annotated types and Field descriptions in the handler signature.
    async def find(
        ctx: Context,
        query: Annotated[str, Field(description="What to search for")],
        collection_name: Annotated[
            str, Field(description="The collection to search in")
        ],
        query_filter: ArbitraryFilter | None = None,
    ) -> list[str] | None:
Behavior2/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 of behavioral disclosure. While it mentions what the tool does (look up memories), it lacks critical behavioral details: it doesn't specify whether this is a read-only operation, what permissions might be required, how results are returned (e.g., pagination, format), or any rate limits. For a search tool with zero annotation coverage, this is a significant gap.

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 description is appropriately sized and front-loaded: the first sentence states the core purpose, followed by bullet points for usage guidelines. There's no wasted text. However, the bullet point 'Get some personal information about the user' is somewhat vague and could be more precise, preventing a perfect score.

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?

Given the tool's complexity (search operation with 2 parameters), no annotations, and no output schema, the description is moderately complete. It covers purpose and usage but lacks behavioral transparency and output details. It's adequate as a minimum viable description but has clear gaps that would hinder an agent's understanding of how to properly invoke and interpret results from this tool.

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?

The schema description coverage is 100%, so the schema already fully documents both parameters (query and collection_name). The description adds no additional parameter semantics beyond what's in the schema. According to the rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 clearly states the tool's purpose: 'Look up memories in Qdrant' specifies the verb (look up) and resource (memories in Qdrant). It distinguishes from the sibling tool 'qdrant-store' by focusing on retrieval rather than storage. However, it doesn't explicitly contrast with the sibling, so it's not a perfect 5.

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 description provides explicit usage scenarios: 'when you need to: - Find memories by their content - Access memories for further analysis - Get some personal information about the user'. This gives clear context for when to use the tool. However, it doesn't mention when NOT to use it or explicitly reference the sibling alternative 'qdrant-store', so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/qdrant/mcp-server-qdrant'

If you have feedback or need assistance with the MCP directory API, please join our Discord server