Skip to main content
Glama

list_tasks

Retrieve all tasks from a specified board in FluentBoards project management to view, organize, or manage workflow items.

Instructions

List tasks in a board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
board_idYesBoard ID

Implementation Reference

  • The handler function for the 'list_tasks' tool. It extracts the board_id from arguments, fetches the list of tasks from the API endpoint `/projects/${board_id}/tasks`, formats the response using formatResponse, and returns it.
    async (args) => {
      const { board_id } = args;
      const response = await api.get(`/projects/${board_id}/tasks`);
      return formatResponse(response.data);
    }
  • Zod input schema for the 'list_tasks' tool, defining a required positive integer board_id.
    {
      board_id: z.number().int().positive().describe("Board ID"),
    },
  • Registration of the 'list_tasks' tool on the MCP server using server.tool(), including name, description, input schema, and inline handler function.
    server.tool(
      "list_tasks",
      "List tasks in a board",
      {
        board_id: z.number().int().positive().describe("Board ID"),
      },
      async (args) => {
        const { board_id } = args;
        const response = await api.get(`/projects/${board_id}/tasks`);
        return formatResponse(response.data);
      }
    );
  • src/index.ts:23-23 (registration)
    Invocation of registerTaskTools on the main MCP server instance, which registers the 'list_tasks' tool among others.
    registerTaskTools(server);
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 action but doesn't cover critical aspects like whether it's read-only, pagination behavior, error handling, or authentication needs. For a list operation with zero annotation coverage, this is a significant gap in transparency.

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 a single, efficient sentence with no wasted words, making it appropriately concise. However, it could be more front-loaded with key details, but it's structurally sound for its simplicity.

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 complexity of listing tasks in a system with multiple sibling tools, no annotations, and no output schema, the description is incomplete. It lacks information on return values, error cases, or how it fits into the broader toolset, leaving gaps for an AI agent to understand its full context.

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 the input schema already documents the 'board_id' parameter fully. The description adds no additional meaning beyond what the schema provides, such as context on board selection or relationships. Baseline 3 is appropriate when the schema handles parameter documentation.

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 'List tasks in a board' clearly states the action (list) and resource (tasks), but it's vague about scope and lacks differentiation from siblings like 'get_task' or 'get_board'. It doesn't specify whether it lists all tasks or filtered ones, making it minimally adequate but with clear gaps.

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?

No guidance is provided on when to use this tool versus alternatives such as 'get_task' (for a single task) or 'get_board' (for board details). The description implies usage for listing tasks but offers no context on prerequisites, exclusions, or comparisons with sibling tools.

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