Update to Real-Time LCA MCP Server

{
  "name": "rtlca-map-material",
  "description": "Use when a user asks to map, remap, assign, link, or connect RTLCA project inventory materials to EPDs. Guides safe manual mapping: resolving project materials, checking lifetimes and quantities, finding relevant EPDs, handling compatible declared units including mass-volume density conversion between kg/g/t and m3, confirming writes with the user, mapping via rtlca_map_materials, and verifying the final mapping and lifetime.",
  "included_files": [],
  "skill_md_contents": "---\nname: rtlca-map-material\ndescription: >-\n  Use when a user asks to map, remap, assign, link, or connect RTLCA project\n  inventory materials to EPDs. Guides safe manual mapping: resolving project\n  materials, checking lifetimes and quantities, finding relevant EPDs, handling\n  compatible declared units including mass-volume density conversion between\n  kg/g/t and m3, confirming writes with the user, mapping via\n  rtlca_map_materials, and verifying the final mapping and lifetime.\n---\n\n# RTLCA Map Material\n\nUse this skill for manual, user-approved mapping of RTLCA project inventory materials to EPDs.\n\nDo not call automapping tools from this skill. Every mapping or remapping must be deliberate, specific, and verified afterward.\n\n## Core Rules\n\n1. Never call `rtlca_map_materials` unless the user has explicitly approved the exact project material to EPD mapping.\n\n2. Treat remapping differently from mapping.\n   - Mapping an unmapped material may increase mapping coverage.\n   - Remapping an already mapped material usually changes GWP but not coverage.\n   - Always report whether the target was previously mapped.\n\n3. Check quantity and lifetime before mapping.\n   - The target inventory material must have a non-zero quantity in a compatible unit.\n   - The material must have a non-zero `lifeTime`.\n   - If lifetime is missing, set or request the correct lifetime before mapping.\n\n4. Declared-unit compatibility.\n   - Mass and volume are cross-compatible: `G`, `KG`, `T` and `M3`.\n   - This works because RTLCA can normalize through EPD density/mass metadata.\n   - Strict units: `M2` maps only to `M2`, `M` maps only to `M`, and `PCS` maps only to `PCS`.\n   - Do not reject a kg EPD for an m3 inventory material, or an m3 EPD for a kg inventory material, if the EPD has density/mass metadata.\n   - If a mass-volume mapping fails, check whether the EPD is missing density/mass metadata before assuming incompatibility.\n\n## Workflow\n\n1. Resolve the project.\n   - Use `rtlca_list_projects` if the project ID is unknown.\n   - Confirm ambiguous project matches.\n\n2. Resolve target inventory materials.\n   - Prefer `rtlca_get_inventory_materials` for flat material lookup.\n   - Search by material name, type identifier, or category.\n   - Collect `materialId`, `identifier`, `typeIdentifier`, `branchName`, `category`, quantities and preferred unit, `lifeTime`, current `mappedEpd`, and `includeMapping`.\n\n3. Resolve declared unit labels.\n   - Call `rtlca_get_declared_units`.\n   - Do not hard-code enum labels.\n   - Determine whether the material has a non-zero quantity in the exact strict unit or in the mass-volume compatibility group.\n\n4. Find candidate EPDs.\n   - Start with `rtlca_find_relevant_epd_materials`.\n   - Build the search description from `identifier`, `typeIdentifier`, `category`, `branchName`, and useful synonyms.\n   - Use the material's preferred unit.\n   - For mass/volume materials, one relevance-finder call is enough because the tool expands across the mass-volume group.\n   - For strict `rtlca_search_materials` searches, remember declared-unit filtering is exact.\n\n5. Present shortlist.\n   - Show 3-8 candidates.\n   - Include EPD name, owner, declared unit, density/mass metadata when relevant, and EPD id.\n   - Prefer locally appropriate EPDs, but do not hide better user-requested manufacturer EPDs.\n\n6. Confirm before writing.\n   - State the inventory material, current mapping if any, target EPD, whether this is mapping or remapping, lifetime, and unit conversion if any.\n   - Wait for explicit approval unless the user's message already clearly says to map this exact material to this exact EPD.\n\n7. Map.\n   - Call `rtlca_map_materials` with `materialId`, `mappedMaterialId`, and `includeMapping: true` unless the user says otherwise.\n   - Do not set `isAutoMapping`.\n\n8. Verify.\n   - Re-fetch the mapped inventory row with `rtlca_get_inventory_materials`.\n   - Confirm `isMapped: true`, `mappedEpd.id`, `mappedEpd.name`, `lifeTime`, and `includeMapping`.\n   - If possible, report whether mapping coverage changed. For remaps, say coverage likely did not change.\n\n9. Handle errors.\n   - If the error says incompatible units or lifespan not set, first check `lifeTime`.\n   - Then check unit compatibility.\n   - Remember mass-volume is allowed if density/mass metadata exists.\n   - If kg-to-m3 or m3-to-kg fails despite density metadata, flag it as a possible backend or tool regression.\n\n## Output\n\nAfter mapping, respond with the mapped material row, previous EPD if any, new EPD, lifetime after mapping, whether it was a map or remap, and verification result.\n\nKeep it short unless the user asks for full details.\n"
}