@seosiri/stal-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_stal_pipelineC | Executes the unified SEOSIRI Theranostic Autonomous Loop: performs zero-trust PII scrubbing, bioassay target validation, biopharma molecular synthesis, and biorobotics surgical kinematic pathing with metered transaction logging. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool, so there is no risk of selecting the wrong tool when multiple overlapping tools exist. The agent cannot confuse it with another tool in this server.
The single tool follows a clear snake_case verb_noun pattern: execute_stal_pipeline. There are no mixed conventions or deviations to evaluate.
One tool is too few for a pipeline that spans PII scrubbing, bioassay validation, molecular synthesis, surgical pathing, and transaction logging. These are distinct stages that would benefit from separate operations, status checks, or configuration tools.
The tool claims to execute the entire autonomous loop, which covers the main happy path. However, there are no tools for status, cancellation, retries, result retrieval, or per-stage control, leaving notable gaps for a complex pipeline.