Skip to main content
Glama

create_task

Add new tasks to project boards in FluentBoards project management system by specifying board ID, title, and optional details.

Instructions

Create a new task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
board_idYesBoard ID
titleYesTask title
descriptionNoTask description
stage_idNoStage ID (optional)

Implementation Reference

  • Registers the MCP 'create_task' tool with input schema validation using Zod and the handler function that builds task data and posts to the project tasks API endpoint.
    server.tool(
      "create_task",
      "Create a new task",
      {
        board_id: z.number().int().positive().describe("Board ID"),
        title: z.string().min(1).describe("Task title"),
        description: z.string().optional().describe("Task description"),
        stage_id: z
          .number()
          .int()
          .positive()
          .optional()
          .describe("Stage ID (optional)"),
      },
      async (args) => {
        const { board_id, title, description, stage_id } = args;
    
        const taskData: any = {
          title,
          board_id,
        };
    
        if (description) {
          taskData.description = formatText(description);
        }
    
        if (stage_id) {
          taskData.stage_id = stage_id;
        }
    
        const response = await api.post(`/projects/${board_id}/tasks`, { task: taskData });
        return formatResponse(response.data);
      }
    );
  • src/index.ts:23-23 (registration)
    Top-level registration call that invokes registerTaskTools on the MCP server, thereby registering the create_task tool among other task tools.
    registerTaskTools(server);
  • Zod schema for CreateTask type definition, matching the input parameters of the create_task tool.
    export const CreateTaskSchema = z.object({
      board_id: z.number().int().positive(),
      title: z.string().min(1),
      description: z.string().optional(),
      stage_id: z.number().int().positive().optional(),
    });
Behavior2/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 of behavioral disclosure. 'Create a new task' implies a write operation, but it doesn't specify permissions required, whether it's idempotent, error handling, or what the response contains (e.g., task ID). This is a significant gap for a mutation tool with zero annotation coverage.

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 extremely concise with a single sentence 'Create a new task', which is front-loaded and wastes no words. It efficiently conveys the core purpose without unnecessary elaboration, earning full marks for brevity.

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 (a mutation with 4 parameters) and lack of annotations and output schema, the description is incomplete. It doesn't cover behavioral aspects like side effects, return values, or error conditions, leaving the agent with insufficient context for reliable use.

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 schema description coverage is 100%, with clear parameter descriptions (e.g., 'Board ID', 'Task title'). The description adds no additional meaning beyond the schema, such as explaining relationships between parameters (e.g., stage_id must belong to board_id). Baseline 3 is appropriate since the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create a new task' states the basic action (create) and resource (task), which is clear but minimal. It doesn't differentiate from sibling tools like 'create_label' or 'create_stage' beyond the resource name, making it somewhat vague in distinguishing its specific purpose within the task management context.

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. For example, it doesn't mention prerequisites (e.g., needing a board_id from 'get_board'), or when to use 'update_task' instead for modifications. This lack of context leaves the agent without usage direction.

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