Think Strategies
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 |
|---|---|
| think-strategiesB | Core thinking tool for structured problem-solving using 10 reasoning strategies. Choose your strategy (linear, chain_of_thought, react, rewoo, scratchpad, self_ask, self_consistency, step_back, tree_of_thoughts, trilemma) and engage in guided thinking with think→act→reflect workflows. Plan actions with 'plannedActions', integrate results with 'actionResults'. Use think-tools for utilities and think-session-manager for session persistence. |
| think-toolsC | Utilities for thinking workflows: connect to MCP servers, execute actions, check status, create branches |
| think-session-managerC | Manage thinking sessions: list with pagination/filtering, search by content, get detailed analysis, or resume previous sessions |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| documentation | |
| strategy-config |
TDQS
Scored across 3 tools
The three tools have distinct primary purposes: session management, core thinking strategies, and workflow utilities. However, there is some overlap between 'think-strategies' and 'think-tools' regarding action execution and integration, which could cause minor confusion about which tool to use for specific tasks like executing actions or handling results.
All tool names follow a consistent 'think-' prefix pattern with descriptive suffixes (session-manager, strategies, tools). This creates a clear, predictable naming convention that helps agents identify the toolset as part of a coherent system.
With 3 tools, this is well-scoped for a thinking strategies server. Each tool serves a distinct functional area (session management, reasoning strategies, utilities), and the count is appropriate for covering the domain without being overwhelming or insufficient.
The toolset covers core aspects of structured thinking: strategy selection, session persistence, and workflow utilities. A minor gap exists in direct manipulation of thinking artifacts (e.g., editing or deleting sessions), but the tools support the main think→act→reflect workflows adequately for most agent use cases.