Skip to main content
Glama
jgsteeler

ChurnFlow MCP Server

by jgsteeler

list_trackers

Display available productivity trackers with their context types and current status to help organize tasks and ideas efficiently.

Instructions

List available trackers with their context types and status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contextNoFilter by context type (business, personal, project, system)

Implementation Reference

  • The handler function that executes the list_trackers tool. It lists available trackers from the capture engine's tracker manager, optionally filtered by the provided context argument, and returns a formatted text response.
    /**
     * Handle list_trackers tool requests
     */
    async function handleListTrackers(args: any): Promise<CallToolResult> {
      try {
        await initializeCaptureEngine();
        
        if (!captureEngine) {
          throw new Error('Failed to initialize capture engine');
        }
    
        // Get all trackers through the capture engine's tracker manager
        const trackers = captureEngine['trackerManager']?.getTrackersByContext() || [];
        
        let filteredTrackers = trackers;
        if (args.context) {
          filteredTrackers = trackers.filter((tracker: any) => 
            tracker.frontmatter.contextType === args.context
          );
        }
    
        const trackerLines = [
          '📚 Available Trackers',
          '',
        ];
    
        if (filteredTrackers.length === 0) {
          trackerLines.push('No trackers found matching criteria.');
        } else {
          filteredTrackers.forEach((tracker: any) => {
            const context = tracker.frontmatter.contextType || 'undefined';
            const mode = tracker.frontmatter.mode || 'standard';
            trackerLines.push(`📁 ${tracker.frontmatter.tag} (${tracker.frontmatter.friendlyName})`);
            trackerLines.push(`   Context: ${context} | Mode: ${mode}`);
            if (tracker.frontmatter.collection) {
              trackerLines.push(`   Collection: ${tracker.frontmatter.collection}`);
            }
            trackerLines.push('');
          });
        }
    
        return {
          content: [
            {
              type: 'text',
              text: trackerLines.join('\n'),
            },
          ],
          isError: false,
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error listing trackers: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
          isError: true,
        };
      }
    }
  • src/index.ts:68-80 (registration)
    Registration of the list_trackers tool in the TOOLS array, including its name, description, and input schema. This array is returned by the list tools handler.
    {
      name: 'list_trackers',
      description: 'List available trackers with their context types and status',
      inputSchema: {
        type: 'object',
        properties: {
          context: {
            type: 'string',
            description: 'Filter by context type (business, personal, project, system)',
          },
        },
      },
    },
  • Input schema defining the optional 'context' parameter for filtering trackers.
    inputSchema: {
      type: 'object',
      properties: {
        context: {
          type: 'string',
          description: 'Filter by context type (business, personal, project, system)',
        },
      },
    },
  • src/index.ts:344-345 (registration)
    Switch case in the tool call request handler that routes list_trackers calls to the handler function.
    case 'list_trackers':
      return await handleListTrackers(args);
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 'List' implies a read-only operation, it doesn't specify whether this requires authentication, has rate limits, returns paginated results, or what happens when no trackers exist. The description adds minimal behavioral context beyond the basic operation.

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 any unnecessary words. It's appropriately sized for a simple listing 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 simple listing tool with one optional parameter and no output schema, the description is minimally adequate. However, with no annotations and no output schema, it should ideally provide more context about what the returned data looks like and any behavioral constraints. The description covers the basic purpose but leaves gaps in behavioral transparency.

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

Parameters3/5

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

The input schema has 100% description coverage, with the single parameter 'context' clearly documented in the schema. The description doesn't add any parameter information beyond what's already in the schema, so it meets the baseline score of 3 when schema coverage is high.

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 ('List') and resource ('available trackers'), and specifies what information is returned ('with their context types and status'). However, it doesn't explicitly differentiate this listing tool from the 'capture' and 'status' sibling tools, which prevents a perfect score.

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 the 'capture' or 'status' tools. There's no mention of alternatives, prerequisites, or specific scenarios where this listing operation is appropriate versus other operations.

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