agent4.io

add_knowledge_text

Add a text document to a knowledge base (chunking + embedding happen synchronously; returns the real chunk count).

For **local files** (pdf/docx…) see `add_knowledge_file`.

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": {
      "kb_name": "<kb_name>",
      "title": "<title>",
      "content": "<content>"
    },
    "name": "add_knowledge_text"
  }
}

Input Schema

Name	Required	Description	Default
`title`	Yes
`content`	Yes
`kb_name`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral transparency burden. It discloses that chunking and embedding happen synchronously and that the return value is the real chunk count, which is valuable. However, it does not cover error conditions or prerequisites, leaving some gaps.

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 sentences, directly front-loads the core action, and uses structured formatting (bold for 'text') to highlight important context. Every sentence serves a purpose with no fluff.

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 tool with an output schema, the description is fairly complete: it states the operation, synchronous behavior, return value, and alternative for files. It does not mention edge cases like missing knowledge bases or size limits, but these are less critical given the tool's simplicity and output schema existence.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage, and the tool description provides almost no parameter-specific meaning. It implicitly suggests 'content' is text, but there is no explanation of 'kb_name' or 'title' beyond their names, so the description fails to compensate for the schema gaps.

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 adds a text document to a knowledge base, with explicit mention of synchronous chunking and embedding. It also distinguishes itself from the sibling 'add_knowledge_file' by addressing local files separately, making its scope obvious.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage guidance by naming the alternative 'add_knowledge_file' for local files, indicating when to use this tool for text content. It also implies the appropriate context (text vs. files) without ambiguity.

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

All agent4.io tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?