Skip to main content
Glama
Sign In
mcp-1c-local-bridge

mcp-1c-local-bridge

by ntappw
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

query

Execute 1C database requests in the active user session and return results for every statement in a batch, with selectable table or JSON output and optional parameters.

Instructions

Выполняет запрос 1С на сервере с правами пользователя сеанса и возвращает результаты всех запросов пакета.

Значения параметров: строка, число, булево и null передаются как есть, массив - список значений
(для В (&Список)). Особые значения - объекты:
{"_date": "2026-10-21T00:00:00"} - дата (можно "2026-10-21");
{"_type": "Справочник.Контрагенты", "_uuid": "..."} - ссылка; ссылку из результата format=json
можно передать целиком;
{"_type": "Перечисление.ВидыКонтрагентов", "_name": "ЮридическоеЛицо"} - значение перечисления;
{"_predefined": "Справочник.Валюты.Рубль"} - предопределённое значение;
{"_expr": "НачалоГода(ТекущаяДатаСеанса())"} - выражение 1С, вычисленное на сервере.
РАЗРЕШЕННЫЕ и ПЕРВЫЕ в текст не добавляются: пишите их сами.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>"
    },
    "name": "query"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesТекст запроса 1С; пакет из нескольких запросов допустим.
formatNotable - таблицы и сводки для чтения, ссылки показаны представлениями; json - ответ как есть, с типами и UUID ссылок.table
paramsNoПараметры запроса: {"Имя": значение}. Подробности формата - в описании инструмента.
sessionNoСеанс моста: идентификатор из sessions или часть строки соединения, имени конфигурации, пользователя. Не указан - единственный открытый сеанс.
timeoutNoСколько секунд ждать ответ. Команда, которую обработка не начала за это время, снимается; начатая выполняется дальше, её результат забирается инструментом result.
row_limitNoСколько строк каждого результата вернуть.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries full burden: it does disclose the execution context ('с правами пользователя сеанса') and batch return semantics, which is genuine added value. However it never states whether the query is read-only, what permissions/errors can occur, or how failures surface.

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?

Front-loaded with purpose, then a dense but all-useful catalog of value encodings. The closing note about РАЗРЕШЕННЫЕ/ПЕРВЫЕ is a minor but relevant caveat, not filler. Slightly long, but each clause carries information.

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?

Output schema exists and format/enum options are covered, so return-shape explanation isn't needed. Still, for a server-side execution tool with zero annotations, the missing read-only/mutation disclosure and error semantics leaves a real gap an agent would want closed.

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%, but the description goes well beyond it by specifying the encoding of special values — dates, refs, enum values, predefined values, and server-side 1C expressions — plus how arrays map to (&Список). That is exactly the kind of syntax guidance a schema of type 'object' cannot convey.

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?

States a specific action and resource ('Выполняет запрос 1С на сервере') plus scope ('с правами пользователя сеанса') and explicitly notes it returns results of all queries in a batch. It never names the sibling tools (eval/execute/result) to differentiate itself, so it stops short of a 5.

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?

Usage is only implied by the tool's nature — nothing tells the agent when to choose this over eval or execute, or when to hand off to result. The timeout param hints at the result handoff, but that lives in the schema, not the description.

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