Skip to main content
Glama
KlausFreiberufler

DevFlow MCP Server

flow_create

Create a new feature request, bug report, or task with required summary, description, and acceptance criteria to enforce structured development workflows.

Instructions

Create a new flow in a project. Use this to create new feature requests, bug reports, or tasks. The flow starts in 'idea' state by default.

DF-378 — Valid metadata triple required:

  • summary: short one-line title, 3..80 characters (NOT a paragraph)

  • description: detailed body, ≥ 30 characters (the goal, motivation, constraints)

  • acceptanceCriteria: at least 1 testable success criterion, each ≥ 10 characters

If your text is long, put the title into summary (≤ 80 chars) and the body into description. The backend rejects payloads that violate these limits with a structured 400 flow_input_invalid.

Requires a projectId (use project_list to find it).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdNoThe project ID this flow belongs to
summaryYesBrief one-line title (3..80 chars). Long text belongs in `description`, not here.
descriptionYesDetailed body explaining the goal, motivation, and constraints (≥ 30 chars).
flowTypeNoType of flow (default: feature)
acceptanceCriteriaYesList of acceptance criteria (≥ 1 item, each ≥ 10 chars).
Behavior3/5

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

Describes validation requirements and rejection behavior (structured 400). No annotations provided, so description carries burden. Missing output or side-effect details like created flow ID or notifications.

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?

Concise, well-structured with bullet points for requirements. Every sentence adds value. No fluff.

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?

Covers validation rules, default state, and prerequisite. Missing output description (no output schema), and the projectId contradiction reduces completeness. Adequate but not robust.

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

Parameters2/5

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

Adds context on metadata triple and practical tips beyond schema. However, description says 'Requires a projectId' while schema lists projectId as optional, creating a contradiction that undermines trust.

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 it creates a flow in a project and lists use cases (feature requests, bug reports, tasks). It is specific but does not distinguish from sibling 'task_create', which may cause confusion.

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?

Provides explicit instructions on when to use, default state ('idea'), and character limits for fields. Also advises to use 'project_list' to find projectId. Lacks exclusion criteria or alternatives.

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