No user-submitted related servers found.
Scored across 16 tools
Most tools target clearly distinct actions (create/edit/describe device, write data, import file, plot, sq_limit). The main overlap is among the simulation family — scaps_simulate, scaps_batch, scaps_optimize, scaps_run_script — but their descriptions draw usable boundaries (single run, parameter sweep, fitting, escape hatch). Minor potential confusion between scaps_results and scaps_plot, and between scaps_create_device and scaps_edit_device, is resolved by the descriptions.
All tools share the scaps_ prefix and mostly follow verb_noun (write_data, list_files, create_device, edit_device, describe_device, run_script, import_file). A few deviate to bare verbs or nouns (scaps_simulate, scaps_status, scaps_jobs, scaps_results, scaps_batch), but the pattern remains predictable and readable.
16 tools is at the upper end of the comfortable range, but the domain (device construction, simulation, batch/optimization, results, jobs, file management, scripting) genuinely warrants this surface. Each tool maps to a real workflow step rather than padding.
Coverage is strong: create/edit/describe devices, simulate, batch, optimize, retrieve/plot results, manage jobs, import files, query script reference, and a low-level script escape hatch. Gaps are minor — no explicit delete/cleanup of run artifacts and no dedicated material-authoring tool, though scaps_write_data and scaps_edit_device partially cover these.