Skip to main content
Glama
KlausFreiberufler

DevFlow MCP Server

flow_update

Update a flow's state or submit implementation plan, agent summary, and testing instructions to advance it through the DevFlow workflow.

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
prUrlNoGitHub PR URL for this flow
flowIdYesThe flow ID to update
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).
prStateNoGitHub PR state
prNumberNoGitHub PR number for this flow
branchNameNoGit branch name for this flow (required at strictness 4+ when git is enabled)
agentStatusNoOverride for agent status (normally auto-derived, only set if needed)
agentMessageNoOverride for agent message (normally auto-derived, only set if needed)
agentSummaryNoAgent summary after implementation (required for review state)
currentStateNoNew state for the flow
filesChangedNoRepo-relative paths changed by this flow (e.g. from `git diff --name-only origin/main...HEAD`). Required by the adr-compliance gate on review→done when git is enabled.
selfApprovedNoDF-292 — set to true to claim this transition under 'agent_with_discipline' policy. Must be combined with disciplineTokens.
testStrategyNoDF-435 — evidence for devflow-tdd/verification: how the change was tested (commands + results).
acVerificationNoDF-435 — per-AC verification evidence: [{acId, status, evidence}].
disciplineTokensNoDF-292 — signed HMAC tokens (one per required skill) returned by devflow_token_emit. Backend verifies all required tokens before allowing the transition.
acceptanceCriteriaNoList of acceptance criteria
implementationPlanNoMarkdown content of the implementation plan (required for approval state)
planReconciliationNoDF-435 — plan-vs-reality reconciliation: { perAcStatus: [{acId, status}, ...] }.
testingInstructionsNoInstructions for user testing (required for review state). Include what to test, expected behavior, and edge cases.
Behavior4/5

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

With no annotations provided, the description carries the burden. It discloses auto-derivation of agentStatus, mandatory fields for approval/review, commit append behavior, and the docsUpdate blocking condition. This is substantial beyond the schema, though it doesn't cover side effects or failure modes.

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 well-structured with bullet points and an IMPORTANT section, front-loading the primary purpose. Every sentence adds value with no redundancy.

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 tool's complexity (19 params, nested objects, no output schema), the description covers the main use cases, required fields, and key behavioral constraints. It does not explain return values or error scenarios, but the schema covers parameters thoroughly.

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 100%, but the description adds crucial context beyond the schema: which parameters are required for which state transitions, and the auto-derived nature of agentStatus. It also clarifies behavior for commits (appending, review blocking) and testingInstructions requirements.

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 explicitly says 'Update a flow's state or submit deliverables' and enumerates specific uses: changing state through the defined pipeline, submitting an implementation plan, and submitting an agent summary. This clearly distinguishes it from siblings like flow_create and flow_get.

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?

It provides clear context on when to use the tool (state transitions, deliverables) and which parameters are required for specific transitions. However, it does not explicitly exclude alternatives or mention when other tools should be used instead.

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