v8help-mcp

Overview Schema Source Related Servers Discussions Admin

Build

build

Regenerates the 1C:Enterprise syntax help search index by unpacking .hbk files, consolidating Markdown, and reindexing; returns a job ID for async progress tracking.

Instructions

Пересобрать индекс: распаковка .hbk -> консолидация md-корпуса -> индексация.

Выполняется асинхронно: возвращает job_id сразу, результат и прогресс — через build_status. Может занять минуты.

Input Schema

TableJSON Schema

Name	Required	Description
`lang`	No	Язык: ru/en (по умолчанию из конфига).
`force`	No	Пересобрать даже если индекс актуален.
`cleanup`	No	Удалить corpus после индексации.
`sources`	No	Источники для сборки (по умолчанию все из конфига).
`chunk_size`	No	Целевой размер чанка в символах (по умолчанию 1500).
`chunk_overlap`	No	Перекрытие соседних чанков в символах (по умолчанию 200).

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed27 schema fields changedv0.14.0Sep 30, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / chunk_overlap / anyOf

Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / chunk_overlap / default
```
Added value: +null
```

changedInput schema / properties / chunk_overlap / description

Previous value: -"Перекрытие соседних чанков в символах (по умолчанию 200)"New value: +"Перекрытие соседних чанков в символах (по умолчанию 200)."

removedInput schema / properties / chunk_overlap / type
```
Removed value: -"integer"
```

addedInput schema / properties / chunk_size / anyOf

Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / chunk_size / default
```
Added value: +null
```

changedInput schema / properties / chunk_size / description

Previous value: -"Целевой размер чанка в символах (по умолчанию 1500)"New value: +"Целевой размер чанка в символах (по умолчанию 1500)."

removedInput schema / properties / chunk_size / type
```
Removed value: -"integer"
```

addedInput schema / properties / cleanup / anyOf

Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / cleanup / default
```
Added value: +null
```

changedInput schema / properties / cleanup / description

Previous value: -"Удалить corpus после индексации"New value: +"Удалить corpus после индексации."

removedInput schema / properties / cleanup / type
```
Removed value: -"boolean"
```

addedInput schema / properties / force / anyOf

Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / force / default
```
Added value: +null
```

changedInput schema / properties / force / description

Previous value: -"Пересобрать даже если индекс актуален"New value: +"Пересобрать даже если индекс актуален."

removedInput schema / properties / force / type
```
Removed value: -"boolean"
```

addedInput schema / properties / lang / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / lang / default
```
Added value: +null
```

changedInput schema / properties / lang / description

Previous value: -"Язык: ru/en (по умолчанию из конфига)"New value: +"Язык: ru/en (по умолчанию из конфига)."

removedInput schema / properties / lang / type
```
Removed value: -"string"
```

addedInput schema / properties / sources / anyOf

Added value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / sources / default
```
Added value: +null
```

changedInput schema / properties / sources / description

Previous value: -"Источники для сборки (по умолчанию все из конфига)"New value: +"Источники для сборки (по умолчанию все из конфига)."

removedInput schema / properties / sources / items
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / sources / type
```
Removed value: -"array"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

First observedv0.10.0Aug 30, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full burden and does disclose key behavior: asynchronous execution, immediate job_id return, progress/result via build_status, and possible multi-minute duration. It omits the destructive/overwrite nature of a rebuild and any resource or concurrency constraints, which is a notable gap for a mutation tool.

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?

Three tight sentences, front-loaded with the pipeline, then the async contract and duration. Every sentence earns its place and there is no repetition.

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 an async pipeline tool with an output schema covering the job_id return, the description supplies the essential execution model, timing, and status-routing. It would be fully complete with a note on overwriting the existing index and any permission requirements, but the core is present.

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 all six parameters (lang, force, cleanup, sources, chunk_size, chunk_overlap) are documented in the input schema. The description adds no parameter-level detail, so the baseline of 3 applies.

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 names a specific verb and resource ('rebuild the index') and even itemizes the pipeline stages (.hbk unpack -> md-corpus consolidation -> indexing). It is clear what the tool does, though it never states what it is not for relative to siblings like search or discover.

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

Usage Guidelines3/5

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

It implies the tool is used to (re)build the index and explicitly routes status/progress checks to the sibling build_status. However, it never states when a rebuild is warranted versus alternatives, nor when not to use it, leaving selection to inference.

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

Deploy Server