Skip to main content
Glama

list_tasks

Retrieve tasks from TodoPomo MCP Server with optional status and priority filters to manage productivity workflows.

Instructions

List all tasks with optional filtering

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoFilter by status
priorityNoFilter by priority

Implementation Reference

  • Handler for the list_tasks tool: filters tasks by status and priority if provided, otherwise lists all, and returns JSON with tasks and count.
    case "list_tasks": {
      let filteredTasks = data.tasks;
      if (args.status && args.status !== "all") {
        filteredTasks = filteredTasks.filter((t) => t.status === args.status);
      }
      if (args.priority && args.priority !== "all") {
        filteredTasks = filteredTasks.filter(
          (t) => t.priority === args.priority
        );
      }
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(
              { success: true, tasks: filteredTasks, count: filteredTasks.length },
              null,
              2
            ),
          },
        ],
      };
    }
  • src/index.ts:111-129 (registration)
    Registration of the list_tasks tool in the TOOLS array, including name, description, and input schema.
    {
      name: "list_tasks",
      description: "List all tasks with optional filtering",
      inputSchema: {
        type: "object",
        properties: {
          status: {
            type: "string",
            enum: ["pending", "in-progress", "completed", "all"],
            description: "Filter by status",
          },
          priority: {
            type: "string",
            enum: ["low", "medium", "high", "all"],
            description: "Filter by priority",
          },
        },
      },
    },
  • Input schema for list_tasks tool defining optional status and priority filters.
    inputSchema: {
      type: "object",
      properties: {
        status: {
          type: "string",
          enum: ["pending", "in-progress", "completed", "all"],
          description: "Filter by status",
        },
        priority: {
          type: "string",
          enum: ["low", "medium", "high", "all"],
          description: "Filter by priority",
        },
      },
    },
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. It mentions 'optional filtering' but doesn't describe key behaviors like whether this is a read-only operation, if it supports pagination, what the return format is, or any rate limits. For a list tool with no annotations, this is inadequate.

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 front-loads the core purpose ('List all tasks') and adds a useful qualifier ('with optional filtering'). There is no wasted text, making it highly concise and well-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?

Given the lack of annotations and output schema, the description is incomplete. It doesn't address behavioral aspects like read-only nature, return format, or pagination, which are critical for a list operation. The high schema coverage helps with parameters, but overall context is insufficient.

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 both parameters ('status' and 'priority') fully documented in the input schema. The description adds minimal value beyond the schema by mentioning 'optional filtering', but doesn't provide additional semantic context. This meets the baseline for high schema 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 tool's purpose with a specific verb ('List') and resource ('tasks'), and mentions optional filtering. However, it doesn't distinguish this tool from potential sibling list operations (like 'get_pomodoro_stats' which might also list something), so it falls short of 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. With sibling tools like 'get_pomodoro_stats' that might overlap in listing functionality, there's no explicit or implied context for choosing 'list_tasks' over others. This 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/PratyayRajak/todopomo-mcp'

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