Skip to main content
Glama

create_workflow_definition

Create or update workflow definitions in Conductor to automate business processes and orchestrate tasks.

Instructions

Create or update a workflow definition. If the workflow already exists, it will be updated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
definitionYesComplete workflow definition as a JSON object
overwriteNoOverwrite existing definition (default: true)

Implementation Reference

  • Tool schema definition including name, description, input schema with required 'definition' object and optional 'overwrite' boolean.
    {
      name: "create_workflow_definition",
      description:
        "Create or update a workflow definition. If the workflow already exists, it will be updated.",
      inputSchema: {
        type: "object",
        properties: {
          definition: {
            type: "object",
            description: "Complete workflow definition as a JSON object",
          },
          overwrite: {
            type: "boolean",
            description: "Overwrite existing definition (default: true)",
          },
        },
        required: ["definition"],
      },
    },
  • Handler function that executes the tool: extracts 'definition' and 'overwrite' from args, sends POST request to Conductor's /metadata/workflow endpoint, and returns a success message.
    case "create_workflow_definition": {
      const { definition, overwrite = true } = args as any;
      
      const response = await conductorClient.post(
        `/metadata/workflow`,
        definition,
        {
          params: { overwrite },
        }
      );
      
      return {
        content: [
          {
            type: "text",
            text: `Workflow definition created/updated successfully.`,
          },
        ],
      };
    }
  • src/index.ts:598-602 (registration)
    Registration via the tools array returned in ListToolsRequestHandler, which includes the create_workflow_definition tool.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools,
      };
    });
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. It mentions the update behavior if a workflow exists, which is useful, but fails to cover critical aspects: it doesn't specify required permissions, whether changes are reversible, potential side effects, or response format. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its 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 extremely concise—two sentences that directly state the tool's function and its update behavior. Every word earns its place with no redundancy or fluff, making it easy to parse and front-loaded with essential information.

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 tool's complexity (mutation with nested objects) and lack of annotations and output schema, the description is insufficient. It doesn't explain what a 'workflow definition' entails, how to structure the JSON, error conditions, or what the tool returns. For a create/update operation with significant implications, more context is needed to guide effective use.

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?

Schema description coverage is 100%, so the input schema fully documents both parameters ('definition' and 'overwrite'). The description adds no additional parameter semantics beyond what's in the schema—it doesn't explain the structure of the 'definition' object or clarify the 'overwrite' default behavior further. Baseline 3 is appropriate when the schema handles parameter documentation.

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 ('create or update') and resource ('workflow definition'), making the purpose understandable. It distinguishes this tool from read-only siblings like 'get_workflow_definition' by indicating it modifies data. However, it doesn't explicitly differentiate from 'update_task_status' or other mutation tools, keeping it from 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 Guidelines3/5

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

The description implies usage by mentioning that existing workflows will be updated, suggesting it's for both creation and modification scenarios. However, it provides no explicit guidance on when to use this versus alternatives like 'create_task_definition' or 'update_task_status', nor does it mention prerequisites or exclusions, leaving the agent to infer context.

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/opensensor/conductor-mcp'

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