Strest 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 |
|---|---|
| strest_run_scenarioB | Executes a declarative multi-step REST API workflow scenario with automatic variable chaining and schema assertions. |
| strest_templateB | Generates a ready-to-use template for multi-step authentication and CRUD chaining. |
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 2 tools
The two tools have clearly distinct purposes: one executes an existing scenario, while the other generates a template. There is no meaningful overlap or risk of misselection.
Both tools share the strest_ prefix, but only strest_run_scenario follows a clear verb_noun pattern. strest_template is noun-based and breaks the convention, making the naming mixed though still readable.
Two tools is borderline thin for a scenario-execution server. The core actions are covered, but the surface feels minimal and could benefit from validation or inspection helpers.
Running a scenario and generating a template cover the primary workflow, but there is no tool for validating scenarios, listing available scenarios, or inspecting execution details. These gaps may force agents to rely on trial-and-error.