Skip to main content
Glama
its-dart

Dart MCP Server

by its-dart

list_tasks

Retrieve and filter tasks from Dart project management using assignee, status, priority, due date, and more criteria. Simplify task tracking and organization with customizable queries.

Instructions

List tasks from Dart with optional filtering parameters. You can filter by assignee, status, dartboard, priority, due date, and more.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assigneeNoFilter by assignee name or email
assigneeIdNoFilter by assignee ID
dartboardNoFilter by dartboard title
dartboardIdNoFilter by dartboard ID
descriptionNoFilter by description content
dueAtAfterNoFilter by due date after (ISO format)
dueAtBeforeNoFilter by due date before (ISO format)
idsNoFilter by IDs
inTrashNoFilter by trash status
isCompletedNoFilter by completion status
limitNoNumber of results per page
offsetNoInitial index for pagination
parentIdNoFilter by parent task ID
priorityNoFilter by priority
sizeNoFilter by task size
startAtAfterNoFilter by start date after (ISO format)
startAtBeforeNoFilter by start date before (ISO format)
statusNoFilter by status
statusIdNoFilter by status ID
tagNoFilter by tag
tagIdNoFilter by tag ID
titleNoFilter by title
typeNoFilter by task type
typeIdNoFilter by task type ID

Implementation Reference

  • The handler for the "list_tasks" tool within the CallToolRequestSchema switch statement. It invokes TaskService.listTasks with the provided arguments and returns the tasks as a JSON string.
    case LIST_TASKS_TOOL.name: {
      const tasks = await TaskService.listTasks(args);
      return {
        content: [{ type: "text", text: JSON.stringify(tasks, null, 2) }],
      };
    }
  • The tool schema definition for "list_tasks", including name, description, and detailed inputSchema for filtering parameters.
    export const LIST_TASKS_TOOL: Tool = {
      name: "list_tasks",
      description:
        "List tasks from Dart with optional filtering parameters. You can filter by assignee, status, dartboard, priority, due date, and more.",
      inputSchema: {
        type: "object",
        properties: {
          assignee: {
            type: "string",
            description: "Filter by assignee name or email",
          },
          assigneeId: {
            type: "string",
            description: "Filter by assignee ID",
            pattern: "^[a-zA-Z0-9]{12}$",
          },
          dartboard: { type: "string", description: "Filter by dartboard title" },
          dartboardId: {
            type: "string",
            description: "Filter by dartboard ID",
            pattern: "^[a-zA-Z0-9]{12}$",
          },
          description: {
            type: "string",
            description: "Filter by description content",
          },
          dueAtAfter: {
            type: "string",
            description: "Filter by due date after (ISO format)",
          },
          dueAtBefore: {
            type: "string",
            description: "Filter by due date before (ISO format)",
          },
          ids: { type: "string", description: "Filter by IDs" },
          inTrash: { type: "boolean", description: "Filter by trash status" },
          isCompleted: {
            type: "boolean",
            description: "Filter by completion status",
          },
          limit: { type: "number", description: "Number of results per page" },
          offset: { type: "number", description: "Initial index for pagination" },
          parentId: {
            type: "string",
            description: "Filter by parent task ID",
            pattern: "^[a-zA-Z0-9]{12}$",
          },
          priority: { type: "string", description: "Filter by priority" },
          size: { type: "number", description: "Filter by task size" },
          startAtAfter: {
            type: "string",
            description: "Filter by start date after (ISO format)",
          },
          startAtBefore: {
            type: "string",
            description: "Filter by start date before (ISO format)",
          },
          status: { type: "string", description: "Filter by status" },
          statusId: {
            type: "string",
            description: "Filter by status ID",
            pattern: "^[a-zA-Z0-9]{12}$",
          },
          tag: { type: "string", description: "Filter by tag" },
          tagId: {
            type: "string",
            description: "Filter by tag ID",
            pattern: "^[a-zA-Z0-9]{12}$",
          },
          title: { type: "string", description: "Filter by title" },
          type: { type: "string", description: "Filter by task type" },
          typeId: {
            type: "string",
            description: "Filter by task type ID",
            pattern: "^[a-zA-Z0-9]{12}$",
          },
        },
        required: [],
      },
    };
  • index.ts:192-214 (registration)
    Registration of the "list_tasks" tool (as LIST_TASKS_TOOL) in the TOOLS array, which is returned by the ListToolsRequest handler.
    const TOOLS = [
      // Config
      GET_CONFIG_TOOL,
      // Tasks
      CREATE_TASK_TOOL,
      LIST_TASKS_TOOL,
      GET_TASK_TOOL,
      UPDATE_TASK_TOOL,
      DELETE_TASK_TOOL,
      // Docs
      CREATE_DOC_TOOL,
      LIST_DOCS_TOOL,
      GET_DOC_TOOL,
      UPDATE_DOC_TOOL,
      DELETE_DOC_TOOL,
      // Comments
      ADD_TASK_COMMENT_TOOL,
      LIST_TASK_COMMENTS_TOOL,
      // Other
      GET_DARTBOARD_TOOL,
      GET_FOLDER_TOOL,
      GET_VIEW_TOOL,
    ];
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions filtering but doesn't describe pagination behavior (implied by limit/offset parameters), authentication requirements, rate limits, or what happens when no filters are provided. For a list operation with 24 parameters, this leaves significant behavioral gaps.

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 appropriately brief (two sentences) and front-loaded with the core purpose. The second sentence efficiently lists key filter categories without being exhaustive. There's no wasted verbiage, though it could be slightly more structured.

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?

For a tool with 24 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain the return format, pagination strategy, error conditions, or how multiple filters interact. The agent would need to guess about important behavioral aspects despite the comprehensive parameter schema.

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 mentions filtering by assignee, status, dartboard, priority, due date 'and more,' which partially maps to the 24 parameters. However, with 100% schema description coverage, the schema already documents all parameters thoroughly. The description adds minimal value beyond what's in the schema, meeting the baseline for high coverage.

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 verb ('List') and resource ('tasks from Dart'), making the purpose immediately understandable. However, it doesn't distinguish this tool from sibling tools like 'get_task' or 'list_docs' beyond the resource type, which prevents a perfect score.

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 like 'get_task' (for single task retrieval) or 'list_docs' (for different resource types). It mentions filtering capabilities but doesn't help the agent choose between this and other list/retrieval tools in the sibling set.

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

Related 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/its-dart/dart-mcp-server'

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