No user-submitted related servers found.
Scored across 170 tools
Several tools have overlapping purposes that are hard to distinguish without deep CST knowledge: cst_optimizer vs cst_multi_objective_optimizer vs cst_constrained_optimizer, cst_get_farfield vs cst_get_radiation_pattern_3d vs cst_get_pattern_cut, and cst_get_impedance vs cst_get_smith_chart_data vs cst_analyze_impedance. Descriptions help in some cases, but with 170 tools the boundaries between many result-extraction and solver-configuration tools are blurry.
All names use snake_case with a cst_ prefix, which is readable, but the convention mixes verb-first (cst_get_*, cst_create_*, cst_set_*) with noun-first/domain patterns (cst_antenna_patch, cst_array_linear, cst_pcb_create_stackup, cst_matching_l_network, cst_optimizer). The result is a set of multiple sub-conventions rather than one predictable pattern.
170 tools is an extreme over-scoping for a single MCP server; many tools could be consolidated or made into parameters of broader tools. This volume makes tool selection and maintenance impractical for an agent.
The surface covers essentially every stage of the CST workflow: project management, geometry creation, materials, ports, boundaries, mesh, solvers, simulation control, result extraction, antenna templates, arrays, PCB design, and matching networks. No obvious domain lifecycle gaps remain.