MCP tools for 1C — dispatcher

This skill is the single source of truth for the project's MCP server catalog, task→tool mapping, fallback order, and project-index search retries. Detailed per-tool descriptions for each server live in separate files under docs/. Load a specific docs/<server>.md when you are about to call tools from that server and want to tune parameters; the server must be actually available in the current session (its tools are exposed in the tool schema; the mere presence of an entry in mcp-servers.json does not count as availability).

What is mandatory vs. conditional

• Mandatory for risk-bearing 1C work. If a relevant server is exposed, call the fitting MCP tool for BSL / metadata edits or review, metadata XML, forms, integrations, refactoring, performance, runtime errors, platform API checks, impact analysis, syntax / quality validation, and project-memory operations.
• Conditional for external knowledge. Use platform docs, БСП / SSL, and ITS MCP tools when the task depends on versioned platform behavior, reusable БСП APIs, or standards compliance. Do not call them for generic prose cleanup or rule-file editing unless such a fact is actually needed.
• Not required for Markdown / rules / documentation-only work. For rule files, README, commands documentation, and similar prose-only edits, validate structure, links, paths, and internal consistency instead of calling 1C project MCP tools.
• Recommended: reading docs/<server>.md before parameter-rich calls. Reading the schema is for parameter tuning, not a hard gate. Skipping it is acceptable only when the call is genuinely simple (a one-shot lookup with obvious arguments) and you are not invoking a parameter-rich tool listed below.

Parameter-rich tools — read the doc first

For these tools default parameters are usually suboptimal; consult the server's docs/<server>.md before the first call in the session and adjust the parameters to the task:

• 1c-graph-metadata-mcp: search_code (search_type, detail_level), search_metadata (JSON templates), search_metadata_by_description (alpha, use_fuzzy), trace_impact (direction, depth, relationship_types), trace_call_chain (direction, depth), get_object_dossier (sections), business_search (include_structure, filter_type).
• 1c-code-metadata-mcp: metadatasearch (object_type, names_only), get_method_call_hierarchy (direction, depth), graph_dependencies (direction), bsl_scope_members (member_type).

If docs/<server>.md conflicts with the descriptor exposed by the current environment, the environment descriptor wins.