Skip to main content
Glama
jgsteeler

ChurnFlow MCP Server

by jgsteeler

status

Check ChurnFlow system status and tracker information to monitor productivity system operations and task routing.

Instructions

Get ChurnFlow system status and tracker information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler function that fetches system status from CaptureEngine and formats a readable report with initialization check and error handling.
    async function handleStatus(): Promise<CallToolResult> {
      try {
        await initializeCaptureEngine();
        
        if (!captureEngine) {
          throw new Error('Failed to initialize capture engine');
        }
    
        const status = await captureEngine.getStatus();
        
        const statusLines = [
          '📊 ChurnFlow System Status',
          '',
          `🟢 Initialized: ${status.initialized}`,
          `📚 Total Trackers: ${status.totalTrackers}`,
          `⚙️  AI Provider: ${status.aiProvider}`,
          `🎯 Confidence Threshold: ${status.confidenceThreshold}`,
          `📁 Collections Path: ${status.collectionsPath}`,
          '',
          '📋 Trackers by Context:',
        ];
    
        Object.entries(status.trackersByContext || {}).forEach(([context, count]) => {
          statusLines.push(`  ${context}: ${count}`);
        });
    
        return {
          content: [
            {
              type: 'text',
              text: statusLines.join('\n'),
            },
          ],
          isError: false,
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error getting status: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Tool definition including name, description, and input schema (no parameters required). Used for both tool listing and validation.
    {
      name: 'status',
      description: 'Get ChurnFlow system status and tracker information',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • src/index.ts:334-350 (registration)
    MCP server request handler for CallToolRequestSchema that registers and dispatches the 'status' tool call to its handler function.
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      const { name, arguments: args } = request.params;
    
      switch (name) {
        case 'capture':
          return await handleCapture(args);
        
        case 'status':
          return await handleStatus();
        
        case 'list_trackers':
          return await handleListTrackers(args);
        
        default:
          throw new Error(`Unknown tool: ${name}`);
      }
    });
  • src/index.ts:329-331 (registration)
    MCP server request handler for ListToolsRequestSchema that registers the 'status' tool in the available tools list.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools: TOOLS };
    });
  • Helper method in CaptureEngine that computes and returns the core system status data (initialized state, tracker counts by context, config info) used by the status tool.
    getStatus(): Record<string, any> {
      const trackers = this.trackerManager.getTrackersByContext();
    
      return {
        initialized: this.initialized,
        totalTrackers: trackers.length,
        trackersByContext: trackers.reduce(
          (acc, tracker) => {
            const type = tracker.frontmatter.contextType;
            acc[type] = (acc[type] || 0) + 1;
            return acc;
          },
          {} as Record<string, number>,
        ),
        config: {
          collectionsPath: this.config.collectionsPath,
          aiProvider: this.config.aiProvider,
          confidenceThreshold: this.config.confidenceThreshold,
        },
      };
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Get' implies a read operation, the description doesn't specify whether this requires authentication, has rate limits, returns real-time vs cached data, or what format the information comes in. For a status-checking tool with zero annotation coverage, this leaves significant behavioral gaps.

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 the core purpose without unnecessary words. It's appropriately sized for a simple status-checking tool and front-loads 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 status tool with no output schema, the description provides the basic purpose but lacks important context. Without annotations or output schema, it should ideally specify what 'status and tracker information' includes, whether this is a health check or detailed metrics, and what format the response takes. The current description is minimally adequate but has clear gaps.

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 with 100% schema description coverage, so the schema fully documents the parameter situation. The description appropriately doesn't discuss parameters since none exist, earning a baseline 4 for not creating confusion about non-existent parameters.

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 ('ChurnFlow system status and tracker information'), making the purpose understandable. However, it doesn't explicitly differentiate this tool from its siblings 'capture' and 'list_trackers' - while 'list_trackers' seems related to tracker operations, the distinction isn't articulated in the description.

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 its siblings 'capture' and 'list_trackers'. There's no mention of appropriate contexts, prerequisites, or alternative tools for similar functionality, leaving the agent without usage 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/jgsteeler/churnflow-mcp'

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