Skip to main content
Glama

status

Check deployment status of n8n workflows to identify which are deployed and which require deployment.

Instructions

Show deployment status of workflows (which are deployed, which need deployment)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP server registration: handles ListToolsRequest (returns tool definitions including 'status') and CallToolRequest (delegates to ToolHandler.handleTool)
    // Tools handler
    this.server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: getToolDefinitions(),
    }));
    
    this.server.setRequestHandler(CallToolRequestSchema, async (request) => {
      return await this.toolHandler.handleTool(
        request.params.name,
        request.params.arguments
      );
    });
  • Tool schema/definition for 'status': no input params required
    {
      name: 'status',
      description: 'Show deployment status of workflows (which are deployed, which need deployment)',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • ToolHandler.handleTool switch case for 'status': instantiates ChangeTracker and calls getChangeDetails() to produce the status output
    case 'status':
      const changeTracker = new ChangeTracker(this.workflowsPath);
      await changeTracker.initialize();
      const statusDetails = await changeTracker.getChangeDetails();
      return {
        content: [{
          type: 'text',
          text: statusDetails
        }]
      };
  • ChangeTracker.getChangeDetails(): formats the deployment status text based on getDeploymentStatus() results, listing deployed/pending workflows with details
    async getChangeDetails(): Promise<string> {
      const status = await this.getDeploymentStatus();
      
      let output = 'šŸ“Š Workflow Deployment Status\n\n';
      output += `Total Workflows: ${status.total}\n`;
      output += `āœ… Deployed: ${status.deployed}\n`;
      output += `ā³ Pending: ${status.pending}\n\n`;
      
      if (status.pending > 0) {
        output += 'šŸ“ Workflows Needing Deployment:\n';
        for (const workflow of status.workflows) {
          if (workflow.status !== 'deployed') {
            const icon = workflow.status === 'modified' ? 'šŸ“' : 'šŸ†•';
            output += `  ${icon} ${workflow.name}\n`;
            output += `     Modified: ${new Date(workflow.lastModified).toLocaleString()}\n`;
            if (workflow.deployedAt) {
              output += `     Last deployed: ${new Date(workflow.deployedAt).toLocaleString()}\n`;
            }
          }
        }
        output += '\nšŸ’” Run "McFlow deploy" to deploy pending changes\n';
      } else {
        output += '✨ All workflows are up to date!\n';
      }
      
      return output;
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. While it indicates this is a read operation ('Show'), it doesn't disclose important behavioral traits like whether it requires authentication, has rate limits, returns real-time or cached data, or what format the status information takes. The description is minimal and lacks operational context.

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 extremely concise - a single sentence that efficiently communicates the core purpose. Every word earns its place, with no redundant information. It's appropriately sized for a zero-parameter status-checking tool.

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 no annotations, no output schema, and a read operation that likely returns structured status information, the description is incomplete. It doesn't explain what the output looks like, how status is determined, or what 'need deployment' means operationally. For a status-checking tool in a workflow deployment context, more context about the return format and status definitions would be helpful.

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?

With 0 parameters and 100% schema description coverage, the baseline is 4. The description appropriately doesn't discuss parameters since none exist, and the schema already fully documents this. No additional parameter semantics are needed or provided.

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 tool's purpose: 'Show deployment status of workflows' with specific details about what status information is provided ('which are deployed, which need deployment'). It uses a specific verb ('Show') and resource ('deployment status of workflows'), though it doesn't explicitly differentiate from sibling tools like 'deploy' or 'deployed'.

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. With sibling tools like 'deploy', 'deployed', and 'list' available, there's no indication of when this status-checking tool is appropriate versus those other tools for monitoring workflow deployment states.

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