mcp-chain-of-thought
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 |
|---|---|
| plan_taskB | Initialize and detail the task flow, establish clear goals and success criteria, optionally reference existing tasks for continuation planning |
| analyze_taskC | Deeply analyze task requirements and systematically check the codebase, evaluate technical feasibility and potential risks. If code is needed, use pseudocode format providing only high-level logic flow and key steps, avoiding complete code. |
| reflect_taskB | Critically review analysis results, evaluate solution completeness and identify optimization opportunities, ensuring the solution aligns with best practices. If code is needed, use pseudocode format providing only high-level logic flow and key steps, avoiding complete code. |
| split_tasksA | Decompose complex tasks into independent subtasks, establishing dependencies and priorities. updateMode
Key Requirements
|
| list_tasksC | Generate a structured task list, including complete status tracking, priority, and dependencies |
| execute_taskC | Execute a specific task according to the predefined plan, ensuring the output of each step meets quality standards |
| verify_taskC | Comprehensively verify task completion, ensuring all requirements and technical standards are met without missing details |
| complete_taskC | Formally mark a task as completed, generate a detailed completion report, and update the dependency status of related tasks |
| delete_taskA | Delete unfinished tasks, but does not allow deleting completed tasks, ensuring the integrity of system records |
| clear_all_tasksB | Clear unfinished tasks and reset the task list |
| update_taskB | Update task content, including name, description and notes, dependent tasks, related files, implementation guide and verification criteria. Completed tasks only allow updating summary and related files |
| query_taskC | Search tasks by keyword or ID, displaying abbreviated task information |
| get_task_detailC | Get the complete detailed information of a task based on its ID, including unabridged implementation guides and verification criteria, etc. |
| process_thoughtB | Engage in a flexible and evolving thinking process by creating, questioning, validating, and refining ideas to progressively deepen understanding and generate effective solutions. When needing to gather data, analyze, or research, prioritize reviewing relevant project code; if such code doesn't exist, search the web rather than speculating. Set nextThoughtNeeded to false when thinking is sufficient, otherwise adjust total_thoughts to extend the process |
| init_project_rulesB | Initialize project rules. Call this tool when the user requests to generate or initialize the project specification file, or if the user requests to change or update the project specification. |
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 15 tools
The tools have overlapping purposes that could cause confusion, such as 'analyze_task' and 'reflect_task' both involving analysis and pseudocode, and 'list_tasks' and 'query_task' both retrieving task information. However, descriptions help differentiate some tools, like 'execute_task' for action versus 'plan_task' for planning, reducing ambiguity.
Most tools follow a consistent verb_noun pattern (e.g., 'analyze_task', 'list_tasks', 'update_task'), with only minor deviations like 'init_project_rules' using 'init' instead of a more standard verb. The naming is readable and predictable overall, though not perfectly uniform.
With 15 tools, the count is well-scoped for a task management and analysis system. Each tool appears to serve a distinct function in the workflow, from initialization to execution and verification, making the set comprehensive without being excessive.
The tool set provides complete coverage for task lifecycle management, including initialization ('init_project_rules'), planning ('plan_task'), execution ('execute_task'), monitoring ('list_tasks', 'query_task'), and completion ('complete_task', 'verify_task'). No obvious gaps exist, as it supports CRUD operations and advanced features like reflection and splitting.