Skip to main content
Glama

template_get_workflow_status

Check the status of a workflow in Railway.app to monitor deployment progress and verify completion.

Instructions

[API] Get the status of a workflow

⚡️ Best for: ✓ Checking workflow status

⚠️ Not for: × Creating new services

→ Next steps: service_info

→ Related: template_list, template_deploy

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflowIdYesID of the workflow to get the status of

Implementation Reference

  • Tool registration and definition including name, formatted description, input schema, and handler function that delegates to templatesService.
    createTool(
      "template_get_workflow_status",
      formatToolDescription({
        type: 'API',
        description: "Get the status of a workflow",
        bestFor: ["Checking workflow status"],
        notFor: ["Creating new services"],
        relations: {
          nextSteps: ["service_info"],
          related: ["template_list, template_deploy"]
        }
      }),
      {
        workflowId: z.string().describe("ID of the workflow to get the status of")
      },
      async ({ workflowId }) => {
        return templatesService.getWorkflowStatus(workflowId);
      }
    ),
  • Core implementation of workflow status retrieval: calls client API, handles errors and completion status, formats success/error responses.
    async getWorkflowStatus(workflowId: string) {
      const response = await this.client.templates.getWorkflowStatus(workflowId);
    
      if (response.error) {
        return createErrorResponse(`Error with workflow ${workflowId}: ${response.error}`);
      }
    
      if (response.status.toLowerCase() === 'complete') {
        return createSuccessResponse({
          text: `Workflow ${workflowId} completed successfully`,
          data: response
        });
      }
    
      return createSuccessResponse({
        text: `Workflow ${workflowId} is still running. Status: ${response.status}`,
        data: response
      });
    }
  • MCP server registration of all tools, including the templateTools array which contains template_get_workflow_status.
    export function registerAllTools(server: McpServer) {
      // Collect all tools
      const allTools = [
        ...databaseTools,
        ...deploymentTools,
        ...domainTools,
        ...projectTools,
        ...serviceTools,
        ...tcpProxyTools,
        ...variableTools,
        ...configTools,
        ...volumeTools,
        ...templateTools,
      ] as Tool[];
    
      // Register each tool with the server
      allTools.forEach((tool) => {
        server.tool(
          ...tool
        );
      });
    } 
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 is for getting status (implying a read operation) but doesn't mention any behavioral traits like whether it requires authentication, has rate limits, returns real-time or cached data, or what happens if the workflow ID is invalid. The description adds minimal context beyond the basic purpose.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and front-loaded, starting with the core purpose. The use of emojis and bullet points ('⚡️ Best for:', '⚠️ Not for:', '→ Next steps:', '→ Related:') adds structure without unnecessary verbosity. However, the inclusion of 'Next steps: service_info' might be slightly extraneous as it doesn't directly relate to usage guidelines.

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 low complexity (1 parameter, no output schema, no annotations), the description is somewhat complete but has gaps. It covers purpose and basic usage guidelines but lacks behavioral details like error handling or response format. Without annotations or an output schema, the agent might struggle with understanding the full context of the tool's operation.

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 'workflowId' parameter fully documented as 'ID of the workflow to get the status of.' The description doesn't add any additional meaning or context about the parameter beyond what the schema provides, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate.

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: 'Get the status of a workflow' with a specific verb ('Get') and resource ('workflow status'). It distinguishes from some siblings like 'template_deploy' or 'service_create_from_image' by focusing on status retrieval rather than creation or deployment. However, it doesn't explicitly differentiate from 'deployment_status' which might be a similar sibling tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance with 'Best for: Checking workflow status' and 'Not for: Creating new services,' which helps the agent understand appropriate use cases. It also mentions 'Next steps: service_info' and 'Related: template_list, template_deploy' to suggest alternatives and context. However, it doesn't clarify when to use this versus 'deployment_status' or other status-related siblings.

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/epitaphe360/railway-mcp'

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