Skip to main content
Glama
Sign In
mcp-knowledge-server

mcp-knowledge-server

by NavinAnik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

create_collection

Create a new document collection to organize knowledge for semantic search and RAG-based answers. Provide a name and optional description.

Instructions

Create a new document collection.

    Args:
        name: Collection name (alphanumeric, hyphens, underscores).
        description: Optional collection description.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
descriptionNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as error behavior on duplicate names, required permissions, reversibility, or side effects. It only mentions the creation action and parameter names.

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?

The description is concise with a single-line purpose followed by a structured Args block. It is front-loaded with the most important information and contains no wasted words.

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?

For a simple create operation with an output schema, the description adequately covers the purpose and both parameters. However, it lacks behavioral details like duplicate handling or prerequisites, which prevents a perfect score.

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?

The description adds meaningful constraints beyond the schema by specifying that 'name' must be alphanumeric with hyphens and underscores, and clarifies that 'description' is optional. Since schema description coverage is 0%, this compensation is valuable.

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?

The description clearly states 'Create a new document collection' with a specific verb and resource, distinguishing it from siblings such as add_document, delete_collection, and list_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?

The description provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It merely states the action without placing it in the broader workflow of collection management.

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