DevFlow MCP Server

flow_list

List flows as a Markdown table with state, assignee, and title. Filter by your tasks, state, or project to focus on open work and review the backlog.

Instructions

List flows as a Markdown table (ID | State | Assignee | Titel).

Conventions enforced uniformly across the plugin (skill: devflow-flow-display):

⭐ prefix marks flows assigned to / created by the current user
🔒 marks active agent sessions; idle flows have no lock-marker
Done-flows are hidden by default (focus on open work). Pass includeDone=true to see them.
Order matches the browser FlowsPage default (kanban_sort_order ASC for project-scope, updated_at DESC for cross-project).

Use this to find flows to work on or to brief the user on the backlog.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "flow_list"
  }
}

Input Schema

Name	Required	Description
`mine`	No	If true, only return flows assigned to / created by the current user.
`state`	No	Optional state filter
`projectId`	No	Optional project ID to filter flows
`includeDone`	No	If true, include done-flows. Default: false (open backlog only).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv4.35.0Jun 7, 2026

TDQS

A4.2/5.0

Behavior5/5

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

In the absence of annotations, the description thoroughly discloses behavioral traits: output is a Markdown table, conventions (star prefix for user's flows, lock marker for active sessions), default hiding of done-flows, and ordering logic. This fully compensates for missing annotations.

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 concise with two short paragraphs. The first line immediately states the purpose. The second paragraph adds necessary convention details without fluff. It could be slightly more concise but is well-structured.

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?

Despite no output schema, the description specifies the output format (Markdown table with columns). It covers defaults, filtering options, ordering, and usage intent. For a list tool, this provides sufficient context for correct invocation.

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?

With 100% schema description coverage, baseline is 3. The description adds value by explaining the Markdown table format and the default behavior of includeDone (hidden by default). It also reinforces the meaning of the 'mine' parameter with the star prefix convention.

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 that this tool 'List flows as a Markdown table' with specific columns. It distinguishes itself from other tools like flow_get or flow_create by focusing on listing, but does not explicitly differentiate from sibling listing tools.

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 explicitly states 'Use this to find flows to work on or to brief the user on the backlog.' This provides clear usage context. It also mentions the default hiding of done-flows and the includeDone parameter, but does not exclude alternatives or state when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server