Skip to main content
Glama
research-workflow-studio

research-workflow-studio

by BorgDiven

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DBYesAbsolute path to the SQLite database. The browser service and MCP process must use the same database.
WEB_URLYesURL of the Research Workflow Studio web service, for example http://127.0.0.1:8831.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
rws_project_listB

List projects and confirmed foundations.

rws_record_getB

Read one exact record or historical version.

rws_get_contextA

Read concise project/task context, completed facts, pending gaps and suggested actions. Suggestions are not execution authorization.

rws_code_findA

Find existing implementations before building new code. Returns exact identities and declared contracts; supplied check evidence is not independent verification.

rws_result_queryC

Find exact outputs across runs in this project. Retains producer, case, configuration and observation coordinates; never silently merges repeats.

rws_project_createC

Create an independent project and its initial confirmed foundation; no demonstration records are inherited.

rws_research_saveC

Save a research question or optional hypothesis. implementationLinks declares intended uses of exact spec/code revisions before execution; these links are not evidence and do not decide scientific validity.

rws_experiment_saveB

Save an experiment and bind its confirmed project foundation; does not execute it.

rws_code_registerC

Register an immutable code identity and explicit parent references; never reads or runs the path.

rws_run_registerB

Record an actual run and status. Registration never launches a program; producer bindings are immutable.

rws_artifact_registerA

Register an immutable output with its actual producer and configuration. For a legacy output with unresolved provenance, explicitly set provenance=unresolved with source evidence and a description; never invent a producer run. Does not read arbitrary files.

rws_protocol_registerC

Register immutable evaluation metric definitions, preprocessing, aggregation and missing-data policy.

rws_dataset_registerC

Register an immutable dataset version and exact sample IDs.

rws_conversation_saveB

Register an existing conversation reference; does not create or send a chat.

rws_evaluation_importB

Validate and register existing typed evaluation results with fixed protocol/code/input versions; does not compute metrics.

rws_comparison_saveC

Save exact comparison inputs and fixed/varying conditions without moving their original producers.

rws_analysis_saveB

Save observations, interpretation and limitations; manual analysis may omit code.

rws_report_create_revisionC

Create a report version with immutable foundation and transitive evidence snapshots.

rws_spec_saveA

Define a method-level contract before implementation. Saves a new draft or ready revision; implementations pin an exact ready revision. Cases/configurations belong to runs, not method contracts.

rws_server_saveB

Register a versioned local/SSH workspace using an SSH alias, never credentials. Registration does not connect.

rws_repository_saveB

Register an existing checkout and its exact server reference. Does not clone, inspect or change Git.

rws_environment_saveB

Register a versioned execution directory and Python executable in the registered checkout. Does not execute or probe.

rws_usage_saveC

Reference precise artifacts in a target experiment, including cross-project reuse. Original producer remains unchanged.

rws_usage_removeC

Revoke a material usage without deleting source artifacts or other uses.

rws_overview_proposeB

Save a proposed foundation revision for human review; this does not apply it.

rws_overview_applyC

Human review only. MCP cannot approve its own suggestion; use the application review screen.

rws_overview_dismissD

Human review only. MCP cannot approve its own suggestion; use the application review screen.

rws_project_stages_setC

Human-only current-stage decision. Browsing and completed runs never advance stages.

rws_amendment_proposeA

Propose an audited metadata/source/lineage/recovery correction for an exact record. Does not rewrite the source or approve the correction.

rws_amendment_applyB

Human-only approval of an exact pending amendment. Raw records and previous report snapshots remain unchanged.

rws_amendment_dismissA

Human-only dismissal of an exact pending amendment. Keeps the proposal history without applying its patch.

rws_operation_proposeB

Propose a literal reviewed Git/task operation. No execution occurs. Read-only inspections may be claimed by an explicit local runner; workspace/process mutations need exact human approval.

rws_operation_approveA

Human only: approve this exact operation plan. Approval never launches it.

rws_operation_dismissB

Human only: dismiss this exact operation plan. Approval never launches it.

rws_metrics_appendB

Append actual process measurements in batches under the run's pinned processMetrics contract. Identical points deduplicate; conflicting values never overwrite. Does not run a model.

rws_metrics_queryC

Read bounded process series and compatible alignments. Reuse throughSequence on every page; null stays missing, with no interpolation.

rws_metrics_snapshotB

Freeze the selected run metrics through a previously read sequence into one immutable metric-history artifact. Includes complete definitions and points; rejects over 5000 points instead of silently truncating.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.8/5.0

Scored across 37 tools

Disambiguation4/5

Most tools target a distinct entity or lifecycle action, and the descriptions clarify boundaries between registration, querying, proposal, and human-only approval. There is still some potential confusion among the many save/register/propose variants and the three propose/apply/dismiss triads, but the domain objects remain distinguishable.

Naming Consistency4/5

The naming is overwhelmingly consistent: an rws_ prefix plus snake_case entity/action names such as rws_project_create and rws_run_register. A few outliers like rws_get_context, rws_report_create_revision, and rws_project_stages_set break the dominant noun_verb pattern but remain readable.

Tool Count2/5

37 tools is heavy for an MCP surface, even for a broad research lifecycle. Several lifecycle stages are fragmented into multiple tools, especially the propose/apply/dismiss triads, and consolidation would reduce the surface without losing core capability.

Completeness4/5

The surface covers a wide research workflow: project setup, records, code, runs, artifacts, datasets, evaluations, reports, metrics, proposals, and human approvals. Minor gaps remain around explicit retrieval or listing for some entity types, but generic record access and query tools mitigate most dead ends.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues