MCP Dual-Cycle Reasoner
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 |
|---|---|
| start_monitoringB | Start metacognitive monitoring of an agent's cognitive process |
| stop_monitoringA | Stop metacognitive monitoring and get session summary |
| process_trace_updateC | Process a cognitive trace update from the agent (main monitoring function) |
| detect_loopA | Detect if the agent is stuck in a loop using various strategies |
| store_experienceB | Store a case for future case-based reasoning |
| retrieve_similar_casesB | Retrieve similar cases from the case base |
| get_monitoring_statusA | Get current monitoring status and statistics |
| reset_engineA | Reset the dual-cycle engine state |
| configure_detectionB | Configure loop detection parameters and domain-specific progress indicators |
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 9 tools
Most tools have distinct purposes, but there is some potential overlap between 'detect_loop' and 'process_trace_update' as both involve monitoring cognitive processes. The descriptions clarify their roles, with 'detect_loop' focused on loop detection and 'process_trace_update' handling general trace updates, but an agent might occasionally confuse them in practice.
All tool names follow a consistent verb_noun pattern using snake_case, such as 'configure_detection', 'detect_loop', and 'start_monitoring'. This uniformity makes the set predictable and easy to navigate, with no deviations in naming conventions.
With 9 tools, the count is well-scoped for a dual-cycle reasoner server, covering configuration, monitoring, detection, and case management. Each tool appears to serve a specific function without redundancy, making the set appropriately sized for the domain.
The tool set provides comprehensive coverage for metacognitive monitoring and reasoning, including start/stop, detection, status retrieval, and case storage. A minor gap exists in tools for modifying or deleting stored cases, but core workflows are well-supported, allowing agents to work around this limitation.