Skip to main content
Glama
conductor-oss

Conductor MCP Server

task_create_task_definition

Create or update a task definition by specifying name, description, retry count, and timeout settings for Conductor workflows.

Instructions

Creates or updates a task definition.

The task definition should include at minimum:

  • name: The name/type of the task

  • description: A description of what the task does

  • retryCount: Number of retries (default: 3)

  • timeoutSeconds: Task timeout in seconds

  • responseTimeoutSeconds: Response timeout in seconds

Example task definition: { "name": "my_custom_task", "description": "A custom task that processes data", "retryCount": 3, "timeoutSeconds": 300, "responseTimeoutSeconds": 180, "inputKeys": ["input1", "input2"], "outputKeys": ["result"] }

Args: task_definition: A dictionary containing the task definition

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_definitionYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
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. It only states 'Creates or updates' without disclosing whether updates are partial or full replacements, idempotency, or required permissions. For a mutation tool, more detail is needed.

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 well-structured with a clear header, bullet points of minimum fields, and an example. It is front-loaded with purpose, though slightly verbose with the 'Args' line.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema, the description does not need to explain return values. It adequately covers the parameter usage and provides a working example. However, it could mention that the tool can also update existing definitions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, and the description compensates fully by listing minimum fields (name, description, retryCount, etc.) and providing an example. This adds essential meaning beyond the generic object schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Creates or updates a task definition' with specific verb and resource. It distinguishes from sibling read-only tasks like task_get_all_task_definitions.

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 for creating/updating task definitions but does not explicitly state when to use vs. alternatives or provide exclusions. It lacks guidance on idempotency or prerequisites.

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

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