mFlow

create_standalone_status

Add a new custom status (workflow column) to a standalone project. Use update_standalone_status instead to rename/recategorize an existing one, or reorder_standalone_statuses to change column order — this tool only adds a new column.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Status/column display name, e.g. "In Review".
`color`	No	Optional display color for the status badge/column, e.g. a hex code.
`category`	Yes	Which bucket this status rolls up into for summaries and defaults: "todo", "in_progress", or "done".
`agentRole`	No	Optional coding-agent role: "working" = where a linked task is moved when the coding agent starts it, "review" = where it is moved when the agent finishes. One status per role per project, and only in_progress statuses can hold one.
`projectId`	Yes	The project to add the status to, from list_standalone_projects.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 24, 2026

addedInput schema / properties / agentRole

Added value: +{
+  "description": "Optional coding-agent role: \"working\" = where a linked task is moved when the coding agent starts it, \"review\" = where it is moved when the agent finishes. One status per role per project, and only in_progress statuses can hold one.",
+  "enum": [
+    "working",
+    "review"
+  ],
+  "type": "string"
+}

AddedSep 18, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, and the description adds that this tool 'only adds a new column,' clarifying it is a non-destructive creation operation with a limited scope. It does not disclose potential side effects like duplicate-name behavior or effects on existing tasks, but for a creation tool with these annotations, the description provides adequate extra context.

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 two sentences with no filler. The primary action is front-loaded, and the alternative-tool routing is compactly placed in the second sentence. Every word earns its place.

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 creation tool with five well-documented parameters and clear sibling differentiation, the description is complete. It tells the agent exactly when to use this tool, what it does, and which tools cover adjacent operations. No critical information needed to call it correctly is missing.

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 description coverage is 100%, so all five parameters are already documented in the input schema, including enums and examples. The description adds no additional parameter-level meaning, which is acceptable given the schema's thoroughness. Baseline 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 opens with a specific verb and resource: 'Add a new custom status (workflow column) to a standalone project.' It also explicitly distinguishes itself from sibling tools by naming what it does not do (rename/recategorize, reorder), making it immediately clear what this tool is for.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit when-to-use and when-not-to-use guidance: 'Use update_standalone_status instead to rename/recategorize an existing one, or reorder_standalone_statuses to change column order — this tool only adds a new column.' This directly tells the agent which sibling to choose for other operations.

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

All mFlow tools Inspect

Try in Browser

Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?