Skip to main content
Glama

vector_collection_management

Create, list, delete collections and add documents in a vector database to support RAG operations.

Instructions

Manage collection management operations.

Actions:

  • 'create_collection': Creates a new collection or retrieves an existing one in the vector database.

  • 'add_documents': Adds documents to an existing collection in the vector database.

  • 'delete_collection': Deletes a collection from the vector database.

  • 'list_collections': Lists all collections in the vector database.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform. Must be one of: 'create_collection', 'add_documents', 'delete_collection', 'list_collections'
db_typeNodb type
db_pathNodb path
hostNohost
portNoport
db_nameNodb name
usernameNousername
passwordNopassword
collection_nameNocollection name
overwriteNooverwrite
document_directoryNodocument directory
document_pathsNodocument paths
document_contentsNodocument contents
confirmNoconfirm

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations provided, so the description carries full burden. It mentions 'delete_collection' as an action but does not disclose that deletion is destructive or irreversible. It also fails to mention authentication requirements, rate limits, or side effects of adding documents.

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 a concise bullet list of actions, front-loading the main purpose. It uses minimal wording and is easy to scan. Every sentence serves a purpose.

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?

Despite high parameter count (14) and no output schema provided (though context says one exists), the description lacks parameter-to-action mappings, usage examples, and behavioral context. It does not explain which parameters are relevant for each action, leaving the agent to rely solely on schema.

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 baseline is 3. The description lists actions but does not add meaning beyond the schema. Many parameter descriptions (e.g., 'db type', 'host') are vague and not enhanced by 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 states the tool handles collection management operations and lists four distinct actions with clear names (create_collection, add_documents, delete_collection, list_collections). However, it doesn't explicitly distinguish this tool from its sibling 'vector_search', which may also involve collections.

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?

There is no guidance on when to use this tool versus alternatives like vector_search. The description does not specify prerequisites, contexts, or exclude scenarios, leaving the agent to infer usage without support.

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/Knuckles-Team/vector-mcp'

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