Skip to main content
Glama
uk-kd

operbots-mcp

by uk-kd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Создать или настроить базу знаний

knowledge_save

Create a knowledge base or update its settings, including chunk size, overlap, score threshold, active status, and AI vector provider for search.

Instructions

Без параметра base создаёт базу, с параметром — меняет её настройки. Для поиска базе нужно подключение к ИИ-сервису, умеющему считать векторы. Подключение можно сменить или снять (provider=null) только у пустой базы: векторы разных моделей несопоставимы. После правки размера куска старые материалы нужно пересобрать через knowledge_reindex.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
baseNoКакую базу менять. Не указывайте, чтобы создать новую.
caseNoДело: название или идентификатор. Если не указать, берётся дело по умолчанию, иначе последнее открытое в панели.
nameNoНазвание базы.
top_kNoСколько фрагментов подмешивать в ответ. По умолчанию 4.
activeNoВключена ли база. Выключенная не ищет.
providerNoПодключение к ИИ-сервису для векторов: название или идентификатор. null — отвязать сервис от базы; после этого поиск не работает, пока не выбран новый.
min_scoreNoПорог близости: ниже него фрагмент не берётся. По умолчанию 0.25.
chunk_sizeNoРазмер куска в символах. По умолчанию 900.
descriptionNoДля чего она. null — стереть.
chunk_overlapNoНахлёст между кусками. По умолчанию 120.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.0
    • addedInput schema / properties / description / anyOf
      Added value: +[
+  {
+    "maxLength": 2000,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / description / description
      Previous value: -"Для чего она."New value: +"Для чего она. null — стереть."
    • removedInput schema / properties / description / maxLength
      Removed value: -2000
    • removedInput schema / properties / description / type
      Removed value: -"string"
  2. Changed2 schema fields changedv0.1.14
    • changedInput schema / properties / provider / description
      Previous value: -"Подключение к ИИ-сервису для векторов: название или идентификатор."New value: +"Подключение к ИИ-сервису для векторов: название или идентификатор. null — отвязать сервис от базы; после этого поиск не работает, пока не выбран новый."
    • changedInput schema / properties / provider / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
  3. First observedv0.1.1

TDQS

A4.8/5.0
Behavior5/5

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

Adds non-obvious behavioral constraints well beyond the annotations: the provider can only be swapped or detached on an empty base because vectors from different models are incomparable, and changing chunk_size invalidates existing materials until a reindex. The annotations only supply the generic write/openWorld profile; the description supplies the domain rules.

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?

Four short sentences, front-loaded with the create-vs-update rule, then the provider constraint, then the reindex note. Every sentence carries a distinct, actionable fact with no repetition of schema text.

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 10-parameter, no-output-schema mutation tool this covers the critical behaviors (mode selection, provider legality, chunk_size side effect). It omits what happens to unspecified settings on update and whether the operation is atomic, but the annotations and schema carry the rest.

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?

Schema coverage is 100%, so the baseline is 3; the description goes further by explaining the meaning of `base` presence, the `provider=null` detach semantics, and the consequence of `chunk_size`. It does not add syntax beyond the schema, but the extra causal context justifies a step above baseline.

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?

States a specific verb+resource (create or configure a knowledge base) and immediately disambiguates the two modes by the presence of the `base` parameter. An agent can distinguish this from knowledge_add_document, knowledge_reindex, and knowledge_delete without opening any schema.

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?

Explicitly states when to omit `base` (create) vs supply it (configure), and names the alternative `knowledge_reindex` for the case where chunk_size was changed. It also flags the provider=null path and its consequence, so the agent knows when that operation is legal.

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