Skip to main content
Glama

configure_tracking

Set up global workflow tracking to monitor node outputs, enable checkpoints, and track errors for improved debugging and workflow management.

Instructions

Configure global tracking settings for workflows

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
enabledNoEnable or disable tracking globally
storageUrlNoBase URL for storage API
trackAllNodesNoTrack all node outputs (can be verbose)
enableCheckpointsNoEnable checkpoint system
enableErrorTrackingNoEnable error tracking

Implementation Reference

  • The executeTool method's switch case that implements the 'configure_tracking' tool logic: updates trackingConfig based on input args, persists to .tracking-config.json, and returns confirmation message.
    case 'configure_tracking':
      // Update global tracking configuration
      this.trackingConfig = {
        enabled: args?.enabled ?? this.trackingConfig.enabled,
        storageUrl: args?.storageUrl || this.trackingConfig.storageUrl,
        trackAllNodes: args?.trackAllNodes ?? this.trackingConfig.trackAllNodes,
        enableCheckpoints: args?.enableCheckpoints ?? this.trackingConfig.enableCheckpoints,
        enableErrorTracking: args?.enableErrorTracking ?? this.trackingConfig.enableErrorTracking
      };
    
      // Save configuration to file for persistence
      const configPath = path.join(this.workflowsPath, '.tracking-config.json');
      await fs.writeFile(configPath, JSON.stringify(this.trackingConfig, null, 2));
    
      return {
        content: [{
          type: 'text',
          text: `✅ Tracking configuration updated:\\n\\n` +
            `Enabled: ${this.trackingConfig.enabled}\\n` +
            `Storage URL: ${this.trackingConfig.storageUrl || 'Not set'}\\n` +
            `Track all nodes: ${this.trackingConfig.trackAllNodes || false}\\n` +
            `Enable checkpoints: ${this.trackingConfig.enableCheckpoints || false}\\n` +
            `Enable error tracking: ${this.trackingConfig.enableErrorTracking || false}\\n\\n` +
            `Configuration saved to ${configPath}`
        }]
      };
  • The tool definition object including name, description, and inputSchema for 'configure_tracking'.
      name: 'configure_tracking',
      description: 'Configure global tracking settings for workflows',
      inputSchema: {
        type: 'object',
        properties: {
          enabled: {
            type: 'boolean',
            description: 'Enable or disable tracking globally',
          },
          storageUrl: {
            type: 'string',
            description: 'Base URL for storage API',
          },
          trackAllNodes: {
            type: 'boolean',
            description: 'Track all node outputs (can be verbose)',
          },
          enableCheckpoints: {
            type: 'boolean',
            description: 'Enable checkpoint system',
          },
          enableErrorTracking: {
            type: 'boolean',
            description: 'Enable error tracking',
          },
        },
      },
    },
  • The 'configure_tracking' tool is registered as part of the static tools array exported from registry.ts, used for MCP tool exposure.
        name: 'configure_tracking',
        description: 'Configure global tracking settings for workflows',
        inputSchema: {
          type: 'object',
          properties: {
            enabled: {
              type: 'boolean',
              description: 'Enable or disable tracking globally',
            },
            storageUrl: {
              type: 'string',
              description: 'Base URL for storage API',
            },
            trackAllNodes: {
              type: 'boolean',
              description: 'Track all node outputs (can be verbose)',
            },
            enableCheckpoints: {
              type: 'boolean',
              description: 'Enable checkpoint system',
            },
            enableErrorTracking: {
              type: 'boolean',
              description: 'Enable error tracking',
            },
          },
        },
      },
      {
        name: 'add_checkpoint',
        description: 'Add a checkpoint save/restore capability to a workflow',
        inputSchema: {
          type: 'object',
          properties: {
            path: {
              type: 'string',
              description: 'Path to the workflow file',
            },
            checkpointName: {
              type: 'string',
              description: 'Name for the checkpoint',
            },
            afterNode: {
              type: 'string',
              description: 'Node to add checkpoint after (for saving)',
            },
            addRestore: {
              type: 'boolean',
              description: 'Also add checkpoint restore at workflow start',
            },
          },
          required: ['path', 'checkpointName'],
        },
      },
      {
        name: 'generate_app',
        description: 'Generate a Next.js app for managing workflow data within the current project',
        inputSchema: {
          type: 'object',
          properties: {
            name: {
              type: 'string',
              description: 'Name of the app directory (e.g., "app", "dashboard")',
            },
            stages: {
              type: 'array',
              items: { type: 'string' },
              description: 'Workflow stages for pipeline view (default: created, processing, review, completed)',
            },
            features: {
              type: 'object',
              properties: {
                dashboard: {
                  type: 'boolean',
                  description: 'Include dashboard with stats and tables',
                },
                api: {
                  type: 'boolean',
                  description: 'Include API endpoints for workflow integration',
                },
                database: {
                  type: 'boolean',
                  description: 'Include SQLite database setup',
                },
                webhooks: {
                  type: 'boolean',
                  description: 'Include webhook receivers for n8n',
                },
                approvals: {
                  type: 'boolean',
                  description: 'Include approval/reject functionality',
                },
              },
              description: 'Features to include in the app',
            },
          },
          required: ['name'],
        },
      },
    ];
Behavior2/5

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

With no annotations provided, the description carries full burden but lacks behavioral details. It doesn't disclose whether this is a read-only or destructive operation, what permissions are needed, how changes propagate, or any side effects like rate limits or system impact.

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 directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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?

For a configuration tool with 5 parameters and no annotations or output schema, the description is insufficient. It doesn't cover what 'configure' entails (e.g., persistence, scope), expected outcomes, or error conditions, leaving significant gaps for an AI agent.

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 description adds no parameter-specific information beyond what's in the schema, which has 100% coverage. It doesn't explain interactions between parameters (e.g., how 'enabled' affects others) or provide usage examples. Baseline 3 is appropriate as the schema fully documents 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 'Configure global tracking settings for workflows' clearly states the action (configure) and target (global tracking settings for workflows). It distinguishes from siblings like 'add_tracking' or 'add_checkpoint' by focusing on configuration rather than addition, though it doesn't explicitly contrast with them.

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, when it should be applied (e.g., during setup vs. runtime), or how it relates to siblings like 'add_tracking' or 'activate'.

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/mckinleymedia/mcflow-mcp'

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