Skip to main content
Glama
Sign In
bit-1c-help

bit-1c-help

by firstBitMarksistskaya
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

list_1c_platform_help_sources

List available help sections with their intended use, enabling selection of the right source before searching 1C:Enterprise documentation.

Instructions

Read-only. Список доступных разделов (source) с их назначением (useWhen). Вызывать перед search с фильтром source, чтобы выбрать нужный раздел.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_1c_platform_help_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault
rootNoOptional absolute path to a help directory. Defaults to BIT_1C_HELP_ROOT or ./kb.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden; it opens with 'Read-only' and discloses that the result is a list of sections with their intended use. It could mention error/edge-case behavior, but for a simple listing tool this is sufficient.

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?

Two short, purposeful sentences: the read-only nature is front-loaded, the resource is defined, and the usage context is given. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single optional-parameter listing tool with no output schema, the description explains what is returned, its purpose, and when to call it. The root parameter is already fully documented in the schema.

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% and fully documents the optional root parameter. 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('list') and names the exact resource: available help sections (source) with their purpose (useWhen). It clearly positions itself as a directory tool separate from search/document/section retrieval siblings.

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?

It explicitly says to call this tool before search with a source filter, so an agent knows the correct workflow order and how this tool feeds into search_1c_platform_help.

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