specrun
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 | {} |
| logging | {} |
| prompts | {} |
| resources | {} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| specrun_batchC | Run any SpecRun tool in batch with multiple inputs |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| list_apis | List loaded APIs/tools and ask the user to choose an endpoint. |
| generate_api_call | Collect required inputs for a tool and provide a ready-to-run JSON payload. |
| explain_api_schema | Explain tool parameters and request body schema. |
| generate_random_data | Generate random, ready-to-run JSON payload samples for a tool. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| SpecRun Responses | SpecRun response resources |
TDQS
Scored across 1 tool
Only one tool exists, so there is no ambiguity in tool selection.
The single tool name follows snake_case and verb_noun convention consistently.
With only one tool, the server feels thin for its apparent scope, though the batch tool can handle multiple inputs.
The server lacks individual tools for different SpecRun operations, making it incomplete for fine-grained control.