Skip to main content
Glama
MikeyBeez

MCP Contemplation

by MikeyBeez

help

Access documentation to understand how the contemplation system maintains background cognitive processing, recognizes patterns, and develops insights between conversations.

Instructions

Get help documentation for contemplation system

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The switch case handler for the 'help' tool that returns the static HELP_DOCUMENTATION as a text content response.
    case 'help': {
      return {
        content: [{ type: 'text', text: HELP_DOCUMENTATION }],
      };
    }
  • src/index.ts:481-488 (registration)
    Registration of the 'help' tool in the ListToolsRequestSchema handler, including name, description, and empty input schema (no parameters required).
    {
      name: 'help',
      description: 'Get help documentation for contemplation system',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Input schema for the 'help' tool, which requires no parameters (empty object).
    inputSchema: {
      type: 'object',
      properties: {},
    },
  • Static multiline string containing the full help documentation for all tools, including the 'help' tool description, returned by the handler.
    const HELP_DOCUMENTATION = `
    # MCP Contemplation Server
    
    Interface to Claude's background contemplation loop - a persistent subprocess that:
    - Processes thoughts asynchronously between conversations
    - Works with local Ollama models for different thinking styles
    - Manages context to avoid overflow
    - Saves insights to both temporary scratch and permanent Obsidian storage
    - Learns from usage patterns to improve insight selection
    
    ## Available Functions:
    
    ### start_contemplation()
    Starts the background contemplation loop if not already running.
    Returns: Status message
    
    ### send_thought(thought_type, content, priority?)
    Sends a thought for background processing.
    - thought_type: "pattern", "connection", "question", or "general"
    - content: The thought content to process
    - priority: Optional priority (1-10, default 5)
    Returns: Thought ID for tracking
    
    ### get_insights(thought_type?, limit?, min_significance?)
    Retrieves processed insights from the contemplation loop.
    - thought_type: Optional filter by type
    - limit: Max number of insights (default 10)
    - min_significance: Minimum significance score (default 5)
    Returns: Array of insights with metadata
    
    ### set_threshold(significance_threshold)
    Sets the minimum significance for insights to be returned.
    - significance_threshold: Number 1-10 (default 5)
    Returns: Confirmation message
    
    ### get_memory_stats()
    Gets memory usage statistics for the contemplation system.
    Returns: Stats object with insight counts, memory usage, etc.
    
    ### get_status()
    Gets the current status of the contemplation loop.
    Returns: Status object with running state, queue size, etc.
    
    ### stop_contemplation()
    Gracefully stops the contemplation loop.
    Returns: Status message
    
    ### clear_scratch()
    Clears temporary scratch notes (keeps Obsidian permanent notes).
    Returns: Number of files cleared
    
    ### help()
    Returns this documentation.
    
    ## Thought Types:
    - **pattern**: Notice recurring themes across conversations
    - **connection**: Find links between disparate ideas
    - **question**: Explore interesting questions that arise
    - **general**: Open-ended reflection
    
    ## How It Works:
    The contemplation loop runs as a background process, using local LLMs (via Ollama)
    to process thoughts between conversations. High-significance insights are saved
    permanently to Obsidian, while medium-significance thoughts go to temporary scratch
    storage for 4 days. The system learns which insights prove valuable over time.
    `;
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves help documentation, implying a read-only operation, but doesn't specify format (e.g., text, HTML, structured data), scope (e.g., general vs. specific topics), or any behavioral traits like error handling, response time, or authentication needs. For a tool with zero annotation coverage, this leaves significant gaps in understanding its 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, clear sentence: 'Get help documentation for contemplation system.' It is front-loaded with the core purpose, has zero redundant words, and efficiently communicates the tool's function without unnecessary elaboration. Every word earns its place.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate as a minimum viable explanation. It states what the tool does but lacks details on output format, usage context, or behavioral nuances. For a help tool in a system with siblings like 'get_status', more guidance on when to use it would enhance completeness, but it's not critically incomplete.

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% (as there are no parameters to describe). The description doesn't need to add parameter semantics, so it meets the baseline expectation. No additional value is required or provided beyond the schema's completeness.

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 'Get help documentation for contemplation system' clearly states the verb ('Get') and resource ('help documentation'), specifying the target system ('contemplation system'). It distinguishes from siblings like 'get_status' or 'get_insights' by focusing on documentation rather than system state or data. However, it doesn't explicitly differentiate from potential documentation-related tools that might exist in other contexts.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., whether the system must be running), exclusions (e.g., not for runtime errors), or comparisons to sibling tools like 'get_status' for system state. The agent must infer usage based solely on the tool name and description without explicit context.

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