Skip to main content
Glama
KlausFreiberufler

DevFlow MCP Server

task_create

Create a new task to break down a flow into smaller, trackable steps with summary, description, and acceptance criteria.

Instructions

Create a new task under a flow. Use this to break down a flow into smaller, trackable steps. Tasks can have:

  • Summary (required): Brief description of what to do

  • Description: Detailed implementation notes

  • Acceptance criteria: List of conditions for completion

  • Parent task: For creating sub-tasks

Best practice: Create tasks for each logical step before starting implementation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
flowIdYesThe flow ID this task belongs to
parentIdNoOptional parent task ID for creating sub-tasks
summaryYesBrief description of the task (required)
descriptionNoDetailed description or implementation notes
acceptanceCriteriaNoList of conditions that must be met for task completion
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It fails to mention whether the task is created immediately, validation rules, idempotency, or errors. It also does not describe the return value or side effects.

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 a concise paragraph followed by bullet points. It is front-loaded with purpose and clear. However, some redundancy with the schema could be trimmed without losing clarity.

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?

The description does not explain the tool's response or output behavior. Since there is no output schema, the agent lacks information on whether the created task is returned or just a success indicator. It also omits details like required permissions or flow existence checks.

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 covers 100% of parameters with descriptions. The description adds minimal extra meaning beyond listing fields (e.g., 'Summary (required)') and restates schema info. The 'Parent task' note is already in the schema's parentId description.

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 'Create a new task under a flow,' specifying the action and resource. It differentiates from sibling tools like task_list and task_update by focusing on creation.

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 advises using the tool to 'break down a flow into smaller, trackable steps' and adds a best practice about creating tasks before implementation. However, it does not explicitly compare to alternatives or specify when not to use.

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/KlausFreiberufler/devflow-mcp'

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