mcp-sequentialthinking-qa
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAX_HISTORY_SIZE | No | Maximum number of thoughts to retain in history (default: 1000) | 1000 |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sequentialthinking_qaD | Sequential thinking for QA verification with tool recommendations. |
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
With only one tool, there is no possibility of confusion or overlap between tools. The single tool has a clearly distinct purpose.
The tool name 'sequentialthinking_qa' uses clear snake_case and descriptive terms. With no other tools, consistency is not an issue.
A single tool is insufficient for a QA verification server. While focused, it lacks necessary coverage for common QA operations, making it feel thin.
The server only provides a single tool for sequential thinking, missing obvious operations like running tests, checking results, or managing test cases. This severely limits its utility for QA workflows.