Skip to main content
Glama
sergeyfedyakov

v8help-mcp

by sergeyfedyakov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Search

search

Performs full-text queries against 1C:Enterprise help, returning ranked pages with relevance scores and snippets.

Instructions

Полнотекстовый поиск по справке 1С (FTS5).

Возвращает список страниц с релевантностью (score) и сниппетами.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoФильтр по kind: page/member/index.
limitNoМаксимум результатов.
queryYesПоисковый запрос.
sectionNoФильтр по разделу: objects/tables/lang/query/clang/platform/edt.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changedv0.14.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / kind / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / kind / default
      Added value: +null
    • changedInput schema / properties / kind / description
      Previous value: -"Фильтр по kind: page/member/index"New value: +"Фильтр по kind: page/member/index."
    • removedInput schema / properties / kind / type
      Removed value: -"string"
    • addedInput schema / properties / limit / anyOf
      Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / limit / default
      Added value: +null
    • changedInput schema / properties / limit / description
      Previous value: -"Максимум результатов"New value: +"Максимум результатов."
    • removedInput schema / properties / limit / type
      Removed value: -"integer"
    • changedInput schema / properties / query / description
      Previous value: -"Поисковый запрос"New value: +"Поисковый запрос."
    • addedInput schema / properties / section / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / section / default
      Added value: +null
    • changedInput schema / properties / section / description
      Previous value: -"Фильтр по разделу: objects/tables/lang/query/clang"New value: +"Фильтр по разделу: objects/tables/lang/query/clang/platform/edt."
    • removedInput schema / properties / section / type
      Removed value: -"string"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
  2. First observedv0.10.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does state that results are ranked by relevance and include snippets, which adds useful context, but says nothing about pagination, default limits, permissions, or how the FTS5 scoring behaves.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with zero filler, and the core purpose plus return shape are both front-loaded. It is compact and readable, though slightly terse for a tool with four parameters.

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?

An output schema exists, so return values need not be described at length, and the schema fully covers the inputs. However, the description lacks any routing guidance against siblings like get_page or discover, leaving a gap in overall completeness.

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 the schema already documents query, limit, kind, and section filters in detail. The description adds no parameter meaning beyond what the schema provides, making the baseline 3 appropriate.

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 states a specific verb and resource: full-text search over 1C help using FTS5. It clearly describes the operation and its scope, though it does not explicitly distinguish itself from retrieval siblings like get_page 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 Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives such as get_page, related, or discover. Usage is only implicitly inferable from the word 'search'; no conditions, exclusions, or prerequisites are given.

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