bsl-ls-mcp

bsl_callers

Instructions

Кто вызывает функцию. full_name: 'ОбщийМодуль.МойМодуль.ИмяФункции'. [{name, type, full_name, kind, способ}]: способ "вызов" — граф LSP (Модуль.Метод(...)); "строка" — имя метода строковым литералом ("Модуль.Метод" для ДлительныеОперации, ВыполнитьМетодКонфигурации, в переменной…), такие записи несут "строки" (номера); граф их не видит. Литерал сравнивается целиком без учёта регистра; комментарии не в счёт.

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": {
      "full_name": "<full_name>"
    },
    "name": "bsl_callers"
  }
}

Input Schema

Name	Required	Description	Default
`full_name`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 9, 2026

TDQS

B3.4/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. It usefully discloses that string-literal calls are not seen by the LSP graph, that such records carry source line numbers, that literal matching is case-insensitive, and that comments are excluded. However, it does not state read-only/side-effect behavior or other operational constraints.

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 description front-loads the purpose, then the parameter format, then output semantics. The bracketed schema notation and mixed Russian/English terminology make it denser than ideal, but there is little wasted content.

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?

Given one required parameter and an existing output schema, the definition supplies the parameter format and explains the meaning of the output's 'способ' field and its limitations. It remains complete enough for correct invocation, though sibling routing is absent.

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 single parameter has 0% schema description coverage, so the description must compensate. It gives a concrete full_name format example, 'ОбщийМодуль.МойМодуль.ИмяФункции', which is exactly the kind of syntax clarification needed. Further syntax detail would help, but this is adequate.

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 the operation specifically: it returns who calls a function, and reinforces this with an example full_name and output explanation. It is clear what resource is being queried, but it does not explicitly distinguish itself from the sibling tool bsl_callees.

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 guidance. Usage is only implied by the purpose statement, and the description does not route the agent between bsl_callers, bsl_callees, or bsl_references.

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

Deploy Server