Skip to main content
Glama
KlausFreiberufler

DevFlow MCP Server

flow_update

Update a flow's state through defined stages and submit required deliverables (implementation plan, agent summary) for transitions to approval or review.

Instructions

Update a flow's state or submit deliverables. Use this to:

  • Change flow state (idea -> planning -> approval -> ready -> in_progress -> review -> done)

  • Submit implementation plan for review

  • Submit agent summary after implementation

agentStatus is automatically derived from your tool calls - you don't need to set it manually.

IMPORTANT: Some state transitions require mandatory fields:

  • approval requires: implementationPlan

  • review requires: agentSummary AND testingInstructions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
flowIdYesThe flow ID to update
currentStateNoNew state for the flow
agentStatusNoOverride for agent status (normally auto-derived, only set if needed)
agentMessageNoOverride for agent message (normally auto-derived, only set if needed)
acceptanceCriteriaNoList of acceptance criteria
implementationPlanNoMarkdown content of the implementation plan (required for approval state)
agentSummaryNoAgent summary after implementation (required for review state)
testingInstructionsNoInstructions for user testing (required for review state). Include what to test, expected behavior, and edge cases.
commitsNoList of git commits to add to this flow. New commits are appended to existing ones. TIP: When transitioning to `review`, either include your docs commit(s) here in the same call, OR ensure you have previously registered docs commits on the flow — docsUpdate=5 will block review otherwise. For Git-Discipline 5, at least one commit must be visible on the flow (either in this call or persisted).
branchNameNoGit branch name for this flow (required at strictness 4+ when git is enabled)
prUrlNoGitHub PR URL for this flow
prNumberNoGitHub PR number for this flow
prStateNoGitHub PR state
selfApprovedNoDF-292 — set to true to claim this transition under 'agent_with_discipline' policy. Must be combined with disciplineTokens.
disciplineTokensNoDF-292 — signed HMAC tokens (one per required skill) returned by devflow_token_emit. Backend verifies all required tokens before allowing the transition.
Behavior3/5

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

Discloses that agentStatus is auto-derived and notes required fields for transitions. However, lacking annotations, it doesn't mention error handling, side effects, or auth requirements. Adequate but not thorough.

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?

Well-structured with bullet points and clear sections. Critical information is front-loaded. Every sentence adds value, no fluff.

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?

Covers state machine, required fields, auto-derivation, and commit behavior. No output schema is acceptable. Could include confirmation of success or failure, but overall complete for an update tool.

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

Parameters4/5

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

100% schema coverage provides baseline 3. Description adds value by clarifying auto-derived fields (agentStatus), transition requirements, and commit behavior (appending, docsUpdate tip). Enhances schema guidance.

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?

Description clearly states 'Update a flow's state or submit deliverables' and lists specific state transitions. Differentiates from sibling tools like flow_create or flow_get by focusing on updates.

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 use cases (change state, submit deliverables) and mandatory fields for specific transitions. Could improve by excluding when not to use (e.g., for reading use flow_get), but still clear.

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