Loading ToolBench

Reading the current corpus…

1c-bsp-context MCP server · F · ToolBench

1c-bsp-context

MCP server for indexing and searching 1C:Enterprise Business Solution Platform (BSP) modules, procedures, and subsystems. Provides tools to search procedures, retrieve detailed procedure information, list modules and subsystems, and explore BSP structure.

<=2025-11-25STREAMABLE_HTTP7 tools

49/100

Definition Quality60

Protocol Readiness52

Supportability30

Spec posture

Inferred effective spec <=2025-11-25·current baseline 2026-07-28

Static source inference · medium confidence · detected: Logging

Deprecated protocol patterns detected

Summary

Server provides 7 well-named, read-only tools for BSP library exploration. All tools follow verb_noun naming (search_, get_, list_) and have descriptions (avg 120 chars). Input schemas are present with typed parameters and descriptions. However, output schemas are not documented in the source code provided, parameter descriptions lack format/constraint details (e.g., 'limit' has no min/max), and error handling guidance is absent. No tool annotations (readOnlyHint, etc.) visible. Descriptions are adequate but generic, they state WHAT but not WHEN or WHY to use each tool. This is solid foundational work but lacks the polish of production-grade tools.

Tools (7)

get_bsp_module_inforead only50/100

Retrieve information about a specific BSP module, including its properties, description, and list of exported procedures and functions.

get_bsp_procedure_inforead only50/100

Retrieve detailed information about a specific BSP procedure or function, including parameters, return type, description, examples, warnings, and source code.

get_bsp_subsystem_inforead only50/100

Retrieve detailed information about a specific BSP subsystem, including its modules and child subsystems.

list_bsp_modulesread only50/100

List all available BSP modules with their basic information (name, synonym, subsystem, properties).

list_bsp_subsystemsread only50/100

List all available BSP subsystems with their hierarchy and contained modules.

list_module_proceduresread only50/100

List all procedures and functions in a specific BSP module with optional name filtering.

search_bsp_proceduresread only50/100

Search for procedures and functions in the BSP library by name, description, or module. Supports filtering by subsystem.

Issues (5)

HIGHtool ↗

Output schemas not documented. LLMs cannot plan downstream calls or extract fields without knowing response structure. All 7 tools lack documented return types.

search_bsp_proceduresget_bsp_procedure_infoget_bsp_module_infolist_bsp_moduleslist_bsp_subsystemsget_bsp_subsystem_infolist_module_procedures

HIGHconstrained-input ↗

Parameter constraints missing. 'limit' parameter (1-100, default 20) lacks min/max in schema. 'query' and 'name_filter' lack format/length guidance. LLMs may pass invalid values.

search_bsp_procedureslist_bsp_modulesget_bsp_module_infolist_module_procedures

HIGHrecovery-guide ↗

No error handling guidance. Tools lack recovery hints (e.g., 'If procedure not found, try search_bsp_procedures'). Agents cannot self-correct on failures.

get_bsp_procedure_infoget_bsp_module_infoget_bsp_subsystem_info

Recommendations

Document output schemas for all 7 tools. Example: search_bsp_procedures returns {results: [{name: string, module: string, description: string}], total: number}. This enables LLMs to chain calls and extract fields.
Add min/max constraints to numeric parameters. Change 'limit' description to 'Maximum number of results to return (1-100, default 20)'. Add length/pattern constraints to string params (query, name_filter).
Add recovery hints to get_* tools. E.g., get_bsp_procedure_info: 'If procedure not found, try search_bsp_procedures() with a partial name or keyword.'
Enhance descriptions with WHEN/WHY. E.g., search_bsp_procedures: 'Use this to find procedures by keyword when you don't know the exact name. For a specific procedure, use get_bsp_procedure_info() instead.'
Add readOnlyHint annotations to all tools in the MCP tool registration. This signals to agents that these calls are safe to retry and have no side effects.

Spec posture evidence

Inferred effective spec: <=2025-11-25.

Relies on Logging (deprecated) - log to stderr or use OpenTelemetry

Score history

Overall score trend

First recorded score · v2 rubric

49/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	F	49	<=2025-11-25	v2