Skip to main content
Glama
qdrant

mcp-server-qdrant

Official
by qdrant

qdrant-store

Store information in Qdrant vector collections with metadata for later retrieval, enabling persistent memory storage in MCP applications.

Instructions

Keep the memory for later use, when you are asked to remember something.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
informationYesText to store
collection_nameYesThe collection to store the information in
metadataNoExtra metadata stored along with memorised information. Any json is accepted.

Implementation Reference

  • The main handler function for the "qdrant-store" MCP tool. It defines the input schema via Annotated Fields, processes the information and metadata into an Entry, stores it using the QdrantConnector, and returns a confirmation message.
    async def store(
        ctx: Context,
        information: Annotated[str, Field(description="Text to store")],
        collection_name: Annotated[
            str, Field(description="The collection to store the information in")
        ],
        # The `metadata` parameter is defined as non-optional, but it can be None.
        # If we set it to be optional, some of the MCP clients, like Cursor, cannot
        # handle the optional parameter correctly.
        metadata: Annotated[
            Metadata | None,
            Field(
                description="Extra metadata stored along with memorised information. Any json is accepted."
            ),
        ] = None,
    ) -> str:
        """
        Store some information in Qdrant.
        :param ctx: The context for the request.
        :param information: The information to store.
        :param metadata: JSON metadata to store with the information, optional.
        :param collection_name: The name of the collection to store the information in, optional. If not provided,
                                the default collection is used.
        :return: A message indicating that the information was stored.
        """
        await ctx.debug(f"Storing information {information} in Qdrant")
    
        entry = Entry(content=information, metadata=metadata)
    
        await self.qdrant_connector.store(entry, collection_name=collection_name)
        if collection_name:
            return f"Remembered: {information} in collection {collection_name}"
        return f"Remembered: {information}"
  • Registers the store_foo function (alias and possible wrapper of the store handler) as the MCP tool named "qdrant-store" in the FastMCP server, conditional on read_only being false.
    self.tool(
        store_foo,
        name="qdrant-store",
        description=self.tool_settings.tool_store_description,
    )
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. It mentions storing information for later retrieval, which implies persistence, but doesn't disclose behavioral traits like whether this is a write operation, if it requires specific permissions, how data is indexed, error handling, or rate limits. The description is too brief to provide adequate transparency for a storage tool.

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 very concise (one sentence) and front-loaded with the core purpose. However, it could be more structured by explicitly naming the tool's function (e.g., 'Store information in a Qdrant vector database'). Every word earns its place, but it's slightly under-specified.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a storage tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens after storage (e.g., success confirmation, error responses), how data is organized, or implications for the sibling 'qdrant-find' tool. More context is needed for effective agent use.

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 the schema already documents all three parameters thoroughly. The description doesn't add any meaningful semantic context beyond what's in the schema (e.g., it doesn't explain what 'collection_name' represents in practice or how 'metadata' enhances storage). Baseline 3 is appropriate since the schema does the heavy lifting.

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

Purpose3/5

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

The description states the tool's purpose ('Keep the memory for later use') and mentions the action ('store'), but it's vague about what exactly is being stored and how it relates to the sibling tool 'qdrant-find'. It doesn't specify that this is a vector database storage operation or differentiate it from the find tool.

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?

The description provides minimal guidance ('when you are asked to remember something'), but it doesn't specify when to use this tool versus the sibling 'qdrant-find' tool, nor does it mention any prerequisites, exclusions, or alternative scenarios. No explicit when/when-not instructions are provided.

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