Skip to main content
Glama
Moenamatics

Opus MCP Server

by Moenamatics

initiate_job

Start workflow execution by providing workflow ID, title, and description to create a job with a unique execution ID for tracking.

Instructions

Initiate a new job for a workflow. Returns jobExecutionId required for subsequent operations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflowIdYesThe ID of the workflow to execute
titleYesTitle for the job
descriptionYesDescription for the job

Implementation Reference

  • The main handler function for the 'initiate_job' tool. It extracts workflowId, title, and description from args, sends a POST request to the '/job/initiate' endpoint, and returns the response as formatted text content.
    private async initiateJob(args: any) {
      const { workflowId, title, description } = args;
      const response = await this.axiosInstance.post("/job/initiate", {
        workflowId,
        title,
        description,
      });
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response.data, null, 2),
          },
        ],
      };
    }
  • src/index.ts:130-152 (registration)
    Tool registration in the listTools response, including the name 'initiate_job', description, and input schema defining required parameters.
    {
      name: "initiate_job",
      description:
        "Initiate a new job for a workflow. Returns jobExecutionId required for subsequent operations",
      inputSchema: {
        type: "object",
        properties: {
          workflowId: {
            type: "string",
            description: "The ID of the workflow to execute",
          },
          title: {
            type: "string",
            description: "Title for the job",
          },
          description: {
            type: "string",
            description: "Description for the job",
          },
        },
        required: ["workflowId", "title", "description"],
      },
    },
  • Dispatch case in the CallToolRequestHandler that routes 'initiate_job' calls to the initiateJob method.
    case "initiate_job":
      return await this.initiateJob(args);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool initiates a job and returns an ID, but lacks details on permissions, side effects (e.g., if it starts execution immediately), error handling, or rate limits. This is a significant gap for a mutation tool with zero annotation coverage.

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 front-loaded with the core purpose in the first sentence and adds a critical detail about the return value in the second. Every sentence earns its place with zero waste, making it appropriately sized and efficient.

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 the complexity of initiating a job (a mutation operation) with no annotations and no output schema, the description is incomplete. It doesn't explain what 'initiate' entails (e.g., does it start execution?), potential side effects, or error scenarios, leaving gaps for agent understanding.

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 schema description coverage is 100%, so the schema already documents all three parameters (workflowId, title, description). The description adds no additional meaning beyond what the schema provides, such as format examples or constraints, meeting the baseline for high schema coverage.

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 action ('Initiate a new job') and resource ('for a workflow'), distinguishing it from siblings like 'get_job_status' or 'execute_job'. However, it doesn't explicitly differentiate from 'execute_job' which might be a similar action, leaving some ambiguity.

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 like 'execute_job' or 'get_workflow_details'. It mentions that the returned 'jobExecutionId' is required for subsequent operations, but this is more of a consequence than usage guidance, lacking explicit when/when-not instructions.

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/Moenamatics/Opus-MCP'

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