Skip to main content
Glama

create_stage

Add a new stage to a FluentBoards project board to organize tasks and workflow steps.

Instructions

Create a new stage in a board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
board_idYesBoard ID
titleYesStage title
positionNoStage position (optional)

Implementation Reference

  • The main handler function for the 'create_stage' tool. It destructures the input arguments, validates board access using validateBoardAccess, constructs the stage data (title required, position optional), performs an API POST to `/projects/${board_id}/stage-create`, and returns the formatted response.
    async (args) => {
      const { board_id, title, position } = args;
    
      // Validate board access
      const accessCheck = validateBoardAccess(board_id);
      if (!accessCheck.allowed) {
        return formatResponse(createBoardFocusError(accessCheck));
      }
    
      const stageData: any = {
        title,
      };
    
      if (position !== undefined) {
        stageData.position = position;
      }
    
      const response = await api.post(
        `/projects/${board_id}/stage-create`,
        stageData
      );
      return formatResponse(response.data);
    }
  • Direct registration of the 'create_stage' MCP tool within registerBoardTools, including tool name, description, Zod input schema, and the handler function.
    server.tool(
      "create_stage",
      "Create a new stage in a board",
      {
        board_id: z.number().int().positive().describe("Board ID"),
        title: z.string().min(1).describe("Stage title"),
        position: z.number().optional().describe("Stage position (optional)"),
      },
      async (args) => {
        const { board_id, title, position } = args;
    
        // Validate board access
        const accessCheck = validateBoardAccess(board_id);
        if (!accessCheck.allowed) {
          return formatResponse(createBoardFocusError(accessCheck));
        }
    
        const stageData: any = {
          title,
        };
    
        if (position !== undefined) {
          stageData.position = position;
        }
    
        const response = await api.post(
          `/projects/${board_id}/stage-create`,
          stageData
        );
        return formatResponse(response.data);
      }
    );
  • Zod schema for 'CreateStage' inputs (board_id, title, position), matching the inline schema used in the tool registration. Also used to derive TypeScript type CreateStage.
    export const CreateStageSchema = z.object({
      board_id: z.number().int().positive(),
      title: z.string().min(1),
      position: z.number().optional(),
    });
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool creates a stage but doesn't cover critical aspects like required permissions, whether the operation is idempotent, error conditions, or what happens on success (e.g., returns a stage ID). For a mutation tool, this leaves significant gaps in understanding its behavior.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it easy to parse quickly.

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

Completeness2/5

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

Given the tool's complexity as a mutation operation with no annotations and no output schema, the description is insufficient. It doesn't explain what the tool returns, error handling, or behavioral nuances, leaving the agent with incomplete context for reliable invocation.

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?

The description adds no parameter-specific information beyond what the schema provides. Since schema description coverage is 100%, with clear descriptions for 'board_id', 'title', and 'position', the baseline score of 3 is appropriate—the schema does the heavy lifting, and the description doesn't compensate or add extra meaning.

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 the action ('Create') and resource ('a new stage in a board'), making the purpose immediately understandable. However, it doesn't distinguish this tool from sibling tools like 'create_task' or 'create_label', which also create resources in the same domain, missing an opportunity for differentiation.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing board), exclusions, or how it relates to sibling tools like 'create_task' or 'change_task_status', leaving the agent to infer usage context.

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/danieliser/fluent-boards-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server