comol/ai_rules_1c/1c-meta-info

1c-meta-info — facts about a metadata object

Facts only; a verdict about an object needs the validators of 1c-validate. Search discipline and freshness — content/rules/mcp-first-search.md.

For each graph call, explicitly pass the returned project_id verified against the current source roots; substitute <resolved-project-id> below. Discover through list_graph_projects using the mcp-1c-tools router first when needed. Keep project scope outside JSON query operations and template arguments. An extension requires verified layer coverage/provenance; neither the first project nor the base-only response is an extension lookup. Code-server selectors use their own live schema and mappings (content/rules/multi-contour-search.md).

Address

Graph object lookups accept qualified names such as Справочник.Контрагенты, Документ.РеализацияТоваровУслуг, РегистрНакопления.ТоварыНаСкладах, ОбщийМодуль.РаботаСКонтрагентами. For Code get_metadata_details, reuse the canonical full_path from metadatasearch, for example Документы.НачислениеЗарплаты; a Graph-style singular prefix may cause a slower live-XML fallback. Both calls name the argument object_name, never full_name or object_full_name. Identity tools have their own arguments (resolve_qualified_name takes qualified_name). Invoke-1CEdit.ps1 -Object uses the singular qualified form.

Tools and exact arguments

Calls

{"tool": "get_object_dossier", "args": {"project_id": "<resolved-project-id>", "object_name": "Документ.НачислениеЗарплаты", "sections": ["structure", "forms"]}}
{"tool": "get_metadata_details", "args": {"object_name": "Документы.НачислениеЗарплаты", "sections": "tabular_parts", "detail_level": "outline", "max_items": 200}}
{"tool": "search_metadata_by_description", "args": {"project_id": "<resolved-project-id>", "query": "начисление премии сотрудникам", "filter_type": "Документы", "top_k": 5}}
{"tool": "search_metadata", "args": {"project_id": "<resolved-project-id>", "query": "{\"operation\": \"list_attributes_with_type\", \"type_name\": \"СправочникСсылка.Контрагенты\"}"}}
{"tool": "metadatasearch", "args": {"query": "Контрагенты", "names_only": true, "limit": 5}}

Rules

• Retrieve the smallest projection that answers: names for identification, one section for a field list; never expand a hit into a full dossier without need.
• Page with cursor until complete before claiming an exhaustive list; an empty page section does not prove absence.
• Configurations with extensions: when the graph covers the relevant layers, use one discovered base project_id; effective source version via resolve_effective_entity, layer diff via compare_base_and_extension(object_name, extension_name) — 1c-impact. Uncovered contours use their mapped index or own files; scope and evidence boundaries — content/rules/multi-contour-search.md.
• Typed answers map to actions by code — content/rules/mcp-policy.md → C. Server answers → actions.

Paging contract, JSON operation catalogue, template list: content/skills/mcp-1c-tools/docs/1c-graph-metadata-mcp.md, content/skills/mcp-1c-tools/docs/1c-code-metadata-mcp.md → Reading large metadata objects.