mcp-structured-thinking
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| capture_thoughtB | Stores a new thought in memory and in the thought history and runs a pipeline to classify the thought, return metacognitive feedback, and retrieve relevant thoughts. |
| revise_thoughtC | Revises a thought in memory and in the thought history. |
| retrieve_relevant_thoughtsC | Finds thoughts from long-term storage that share tags with the specified thought. |
| get_thinking_summaryB | Generate a comprehensive summary of the entire thinking process. |
| clear_thinking_historyB | Clear all recorded thoughts and reset the server state. |
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 5 tools
Each tool has a clearly distinct purpose with no ambiguity: capture_thought creates new thoughts, clear_thinking_history resets state, get_thinking_summary generates summaries, retrieve_relevant_thoughts finds related thoughts, and revise_thought updates existing thoughts. The actions (capture, clear, get, retrieve, revise) and targets (thought, history, summary) are well-defined and non-overlapping.
All tools follow a consistent verb_noun pattern with snake_case: capture_thought, clear_thinking_history, get_thinking_summary, retrieve_relevant_thoughts, and revise_thought. The verbs are distinct and appropriate for their actions, and the naming structure is predictable throughout the set.
With 5 tools, this server is well-scoped for its structured thinking domain. Each tool earns its place by covering core operations: creating, revising, retrieving, summarizing, and clearing thoughts. The count is neither too thin nor bloated, fitting typical server ranges (3-15 tools) perfectly.
The tool surface provides complete CRUD/lifecycle coverage for the thought management domain: capture_thought (create), revise_thought (update), retrieve_relevant_thoughts (read), get_thinking_summary (read/analyze), and clear_thinking_history (delete/reset). There are no obvious gaps, and agents can perform full workflows without dead ends.