v8help-mcp

Overview Schema Source Related Servers Discussions Admin

Discover

discover

Shows current configuration and automatically detects local 1C platform install path, 1C:EDT CLI, available LM Studio/Ollama embedders, and index state.

Instructions

Показать конфиг и автодискавери.

Каталог bin установленной платформы 1С (реестр Uninstall/ФС), установка 1C:EDT CLI (1cedtcli), доступные эмбеддеры на localhost-портах (LM Studio/Ollama) и состояние индекса.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.14.0Sep 30, 2026

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

changedOutput schema / (root)

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

First observedv0.10.0Aug 30, 2026

TDQS

B3.4/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 behavioral burden. It implies a read-only reconnaissance operation by listing what it 'shows,' but never states side-effect behavior or prerequisites. The presence of an output schema partly compensates by documenting return values.

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?

The purpose is front-loaded in the first clause, followed by a tight enumerated list of discovered items. It is appropriately sized for a no-argument tool with no redundant filler.

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 zero-parameter discovery tool with an output schema, the description adequately covers what will be surfaced (tools/embedders/index state), and the output schema covers the exact return shape. The only gap is the absence of explicit read-only/behavioral framing in the face of missing annotations.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline is 4. No parameter semantics are fabricated or misrepresented.

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 gives a concrete verb ('Показать') and enumerates the specific resources discovered: the 1C platform bin catalog, 1C:EDT CLI install, embedders on localhost ports (LM Studio/Ollama), and index state. It is far more specific than a tautology, though it does not explicitly differentiate itself from the closest sibling config_get.

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 explicit when-to-use or when-not-to-use guidance and no mention of alternatives among siblings like config_get or config_set. The 'autodiscovery' framing implies it is an environment-reconnaissance/setup step, but the agent must infer this rather than being told.

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

Deploy Server