Skip to main content
Glama
MikeyBeez

MCP Contemplation

by MikeyBeez

stop_contemplation

Terminate ongoing background cognitive processing to halt pattern recognition and insight development between conversations.

Instructions

Stop the contemplation loop

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function that stops the contemplation subprocess by sending a 'stop' action via stdin and then killing the process, returning appropriate status messages.
    async stop(): Promise<string> {
      if (!this.subprocess) {
        return 'Contemplation loop not running';
      }
    
      this.subprocess.stdin?.write(JSON.stringify({ action: 'stop' }) + '\n');
      this.subprocess.kill();
      this.subprocess = undefined;
      
      return 'Contemplation loop stopped';
    }
  • src/index.ts:465-472 (registration)
    Registers the 'stop_contemplation' tool in the MCP server's list of tools, including its description and empty input schema.
    {
      name: 'stop_contemplation',
      description: 'Stop the contemplation loop',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • MCP CallToolRequest handler case that invokes the ContemplationManager.stop() method and formats the response for the protocol.
    case 'stop_contemplation': {
      const result = await contemplation.stop();
      return {
        content: [{ type: 'text', text: result }],
      };
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('stop') but doesn't explain what stopping entails—e.g., whether it halts a process, resets state, requires specific conditions, or has side effects. This leaves significant gaps in understanding the tool's behavior.

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, direct sentence with zero waste—'Stop the contemplation loop'—making it highly concise and front-loaded. Every word contributes to the core purpose without redundancy or fluff.

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

Completeness2/5

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

Given the complexity of a 'stop' action with no annotations or output schema, the description is incomplete. It lacks details on what the contemplation loop is, how stopping affects the system, or what the agent should expect post-execution. This leaves the agent under-informed for effective tool use.

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?

The tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately avoids unnecessary details, earning a baseline score of 4 for this dimension.

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

Purpose3/5

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

The description 'Stop the contemplation loop' clearly indicates the action (stop) and target (contemplation loop), avoiding tautology. However, it lacks specificity about what the 'contemplation loop' entails and doesn't differentiate from sibling tools like 'clear_scratch' or 'start_contemplation', making it vague in context.

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

Usage Guidelines2/5

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

No explicit guidance is provided on when to use this tool versus alternatives. The description implies usage when stopping is needed, but it doesn't specify prerequisites, conditions, or contrast with siblings like 'start_contemplation' or 'set_threshold', leaving the agent without clear contextual direction.

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

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/MikeyBeez/mcp-contemplation'

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