No user-submitted related servers found.
Scored across 82 tools
The set has many overlapping tools for creating/editing variants and for running simulations or preparation flows, such as simulate_template, simulate_design, run_simulation, run_house_task, run_engineering_task, and several create_*_variant tools. Descriptions add boundaries, but an agent must parse dense scope gates to choose correctly, and multiple tools appear to cover closely related project/variant/simulation intents.
Most names use a pvsyst_ prefix and snake_case with a verb_noun pattern, e.g. pvsyst_create_project, pvsyst_update_variant_components, pvsyst_validate_component. A few names are noun phrases or less action-oriented, such as pvsyst_capabilities, pvsyst_license_info, and pvsyst_project_components, but the overall convention remains predictable.
With 82 tools, this is far beyond a well-scoped MCP surface and falls into the extreme mismatch category. Even for a broad PVsyst automation domain, many highly specialized variant-creation and preparation tools make the set hard to navigate.
The surface covers project, variant, component, weather, load/storage, simulation, results, licensing, and engineering review lifecycles with create/read/update/archive/restore operations. Coverage is broad, though many tools explicitly stop at bounded subsets, so the lifecycle is comprehensive but not fully complete for every native PVsyst feature.