Skip to main content
Glama
cyqlelabs

MCP Dual-Cycle Reasoner

by cyqlelabs

get_monitoring_status

Read-onlyIdempotent

Retrieve real-time monitoring status and statistics to identify reasoning loops and enable intelligent recovery within the MCP Dual-Cycle Reasoner server.

Instructions

Get current monitoring status and statistics

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core implementation of getMonitoringStatus() that returns the current monitoring status object with fields: is_monitoring, intervention_count, current_goal, trace_length.
    getMonitoringStatus(): {
      is_monitoring: boolean;
      intervention_count: number;
      current_goal: string;
      trace_length: number;
    } {
      return {
        is_monitoring: this.isMonitoring,
        intervention_count: this.interventionCount,
        current_goal: this.currentTrace.goal,
        trace_length: this.accumulatedActions.length,
      };
    }
  • src/server.ts:590-627 (registration)
    Registers the 'get_monitoring_status' MCP tool including name, description, empty input schema (z.object({})), annotations, and execute handler that delegates to DualCycleEngine.getMonitoringStatus() and returns JSON stringified status.
    private addGetMonitoringStatusTool(): void {
      this.server.addTool({
        name: 'get_monitoring_status',
        description: 'Get current monitoring status and statistics',
        parameters: z.object({}),
        annotations: {
          title: 'Get Monitoring Status',
          readOnlyHint: true,
          destructiveHint: false,
          idempotentHint: true,
          openWorldHint: false,
        },
        execute: async (args, { log, session }) => {
          try {
            const sessionEngine = this.getSessionEngine(session);
            const sessionId = this.sessionIds.get(session);
    
            log.debug('Retrieving monitoring status', { sessionId });
    
            const status = sessionEngine.getMonitoringStatus();
    
            log.info('Monitoring status retrieved', {
              isMonitoring: status.is_monitoring,
              currentGoal: status.current_goal,
              traceLength: status.trace_length,
              interventionCount: status.intervention_count,
              sessionId,
            });
    
            return JSON.stringify(status, null, 2);
          } catch (error) {
            const errorMessage = error instanceof Error ? error.message : String(error);
            log.error('Failed to get monitoring status', { error: errorMessage });
            throw new UserError(`Failed to get monitoring status: ${errorMessage}`);
          }
        },
      });
    }
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false, covering safety and idempotency. The description adds minimal behavioral context beyond this, mentioning 'current' status which implies real-time data but doesn't specify refresh rates, data freshness, or performance characteristics. No contradiction with annotations exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that states exactly what the tool does without any wasted words. It's front-loaded with the core purpose and avoids unnecessary elaboration. Every word earns its place in conveying the essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read operation with comprehensive annotations, the description is minimally adequate. However, without an output schema, it doesn't explain what 'status and statistics' includes (e.g., metrics, health indicators, timestamps). Given the sibling tools suggest a monitoring system context, more detail about the return format would be helpful for agent understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0 parameters and 100% schema description coverage, the baseline is 4 as there are no parameters to document. The description appropriately doesn't mention parameters, focusing instead on what the tool retrieves. No additional parameter semantics are needed or provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Get') and resource ('current monitoring status and statistics'), making the purpose immediately understandable. It doesn't explicitly distinguish from siblings like 'start_monitoring' or 'stop_monitoring', but the 'Get' action differentiates it from mutation tools. The description avoids tautology by specifying what is being retrieved.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for checking current status, but provides no explicit guidance on when to use this versus alternatives like 'start_monitoring' or 'stop_monitoring'. There's no mention of prerequisites, timing considerations, or comparison to sibling tools. The context is clear but lacks specific when/when-not instructions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cyqlelabs/mcp-dual-cycle-reasoner'

If you have feedback or need assistance with the MCP directory API, please join our Discord server