Skip to main content
Glama
Sign In
DevFlow MCP Server

DevFlow MCP Server

by FaerberK
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

task_list

List every task in a flow to show its completion status and hierarchy, helping you track implementation progress across structured development workflows.

Instructions

List all tasks for a flow. Tasks are sub-items of a flow that track implementation progress. Returns tasks with their completion status and hierarchy.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "flowId": "<flowId>"
    },
    "name": "task_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
flowIdYesThe flow ID to list tasks for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.35.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It states the return format (completion status, hierarchy) and implies a read operation, but lacks details on pagination, limits, or authentication requirements.

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 concise (three sentences), front-loaded with the main action, and contains no superfluous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list tool with one parameter and no output schema, the description covers purpose, return type, and relationship to flows completely. No further information is needed.

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?

Schema coverage is 100% with a clear description for flowId. The tool description does not add additional meaning beyond the schema, so baseline score of 3 is appropriate.

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 the verb 'list', the resource 'tasks for a flow', and the returned data (completion status and hierarchy). It distinguishes from sibling tools like task_create and task_update.

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 provides clear usage context: list tasks for a flow. It does not explicitly mention when not to use or alternatives, but as the only tool for listing tasks, the guidance is implicit and adequate.

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

Deploy Server

Other Tools