Knowledge Assistant MCP Server

add_documents

Add text documents to the knowledge base for retrieval and question answering. Use source to label the origin.

Instructions

Add a document (text) to the knowledge base. Use source to label where it came from.

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

Input Schema

Name	Required	Description	Default
`text`	Yes
`source`	No		user_input

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 9, 2026

TDQS

A3.9/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 any behavioral traits beyond the basic action. It does not mention whether the operation is idempotent, requires authentication, overwrites existing documents, or how it handles duplicates—critical context for a write operation.

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 two concise sentences with no filler or redundant information. It front-loads the primary action and then clarifies the optional parameter in a direct, efficient manner.

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?

The tool is simple with only two parameters and an output schema exists, so the description does not need to explain return values. However, the lack of behavioral transparency (e.g., side effects, permissions) leaves gaps for a write operation, making the description minimally complete for its complexity.

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?

With 0% schema description coverage, the description adds value by explaining that 'text' is the document content and 'source' is a label for provenance. This goes beyond the schema's type and default information, providing meaningful semantic context for both parameters.

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 the tool's function: adding a text document to the knowledge base. It uses a specific verb ('Add') and resource ('knowledge base'), and the purpose is distinct from sibling tools that query, search, or approve.

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 clear context that this tool is for adding documents, implying it should be used when you want to insert new content rather than retrieve or edit existing content. It does not explicitly mention alternatives or exclusions, but the purpose is self-evident enough to guide usage.

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

Deploy Server