No user-submitted related servers found.
Scored across 28 tools
Most tools target distinct research-workflow objects and lifecycle actions, with parallel propose/apply/dismiss and save/register families that remain mostly separable through their descriptions. The main ambiguity is between read-oriented tools such as record_get, get_context, result_query, and code_find, and between save/register/import semantics, but these are usually clarified by the tool text.
All tools share the rws_ prefix and generally follow a resource_action pattern such as project_list, experiment_save, and artifact_register. A few deviate, notably rws_get_context and the longer rws_report_create_revision, but the overall convention is predictable.
The 28-tool surface is heavy, but it reflects a broad research lifecycle with projects, experiments, code, runs, artifacts, datasets, protocols, reports, and review workflows. Most tools appear to earn their place, yet the count is large enough to increase selection burden and is above the rubric's typical well-scoped range.
The surface covers a wide CRUD-like and audited lifecycle: project creation/listing, context and record reads, experiment/code/run/artifact/dataset/protocol registration, result querying, analysis and report creation, usage tracking, and amendment/overview review. Minor gaps exist around explicit listing or browsing of some entity types, but read tools and context retrieval provide workarounds.