Skip to main content
Glama

get_waiting_tasks

Retrieve all waiting tasks from Todoist using a specific filter to access task details like content, due dates, priority, and completion status in structured JSON format.

Instructions

Get all waiting tasks from Todoist using the filter "#Waiting | #Brian waiting | #Ansonia Waiting". Returns structured JSON data with task details including id, content, description, completion status, labels, priority, due date, and comment count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_waiting_tasks' tool. It executes getWaitingTasks() from the service layer, formats the result as JSON string in a content block, and returns it.
    handler: async () => {
      console.error('Executing get_waiting_tasks...');
      const result = await getWaitingTasks();
      console.error('get_waiting_tasks completed successfully');
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    },
  • The schema definition for the 'get_waiting_tasks' tool, including name, description, and empty input schema (no parameters required).
    schema: {
      name: 'get_waiting_tasks',
      description:
        'Get all waiting tasks from Todoist using the filter "#Waiting | #Brian waiting | #Ansonia Waiting". Returns structured JSON data with task details including id, content, description, completion status, labels, priority, due date, and comment count.',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
  • Registration of the 'get_waiting_tasks' tool handler in the toolsWithoutArgs registry, which maps tool names to their handler functions for dispatch.
    const toolsWithoutArgs: Record<string, () => Promise<ToolResponse>> = {
      list_personal_inbox_tasks: listPersonalInboxTasksTool.handler,
      list_brian_inbox_per_becky_tasks: listBrianInboxPerBeckyTasksTool.handler,
      list_becky_inbox_per_brian_tasks: listBeckyInboxPerBrianTasksTool.handler,
      list_next_actions: listNextActionsTool.handler,
      get_brian_only_projects: getBrianOnlyProjectsTool.handler,
      get_brian_shared_projects: getBrianSharedProjectsTool.handler,
      get_becky_shared_projects: getBeckySharedProjectsTool.handler,
      get_inbox_projects: getInboxProjectsTool.handler,
      get_context_labels: getContextLabelsTool.handler,
      get_chores_due_today: getChoresDueTodayTool.handler,
      get_tasks_due_tomorrow: getTasksDueTomorrowTool.handler,
      get_tasks_due_this_week: getTasksDueThisWeekTool.handler,
      get_tickler_tasks: getTicklerTasksTool.handler,
      list_gtd_projects: listGtdProjectsTool.handler,
      get_waiting_tasks: getWaitingTasksTool.handler,
      get_recent_media: getRecentMediaTool.handler,
      get_areas_of_focus: getAreasOfFocusTool.handler,
      get_shopping_list: getShoppingListTool.handler,
      list_brian_time_sensitive_tasks: listBrianTimeSensitiveTasksTool.handler,
      list_becky_time_sensitive_tasks: listBeckyTimeSensitiveTasksTool.handler,
    };
  • Core helper function getWaitingTasks() that fetches waiting tasks using the predefined WAITING_FILTER via the generic fetchTasksByFilter, transforming and caching results.
    export async function getWaitingTasks(): Promise<TasksResponse> {
      return await fetchTasksByFilter(WAITING_FILTER, 'get waiting tasks');
    }
Behavior3/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. It discloses that the tool returns structured JSON data with specific task details, which is useful behavioral context. However, it does not mention potential limitations like rate limits, authentication needs, or pagination behavior, leaving gaps for a read operation.

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 efficiently structured in two sentences: the first states the action and filter, and the second details the return data. Every sentence adds value without redundancy, making it front-loaded and appropriately sized for the tool's complexity.

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

Completeness4/5

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

Given the tool has 0 parameters, no annotations, and no output schema, the description provides sufficient context by specifying the filter and return format. It covers the essential aspects for a read operation, though it could be more complete by mentioning authentication or rate limits, but this is minor given the simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately does not add parameter information, maintaining focus on the tool's purpose and output. A baseline of 4 is applied as it compensates adequately for the lack of parameters.

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

Purpose5/5

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

The description clearly states the specific action ('Get all waiting tasks'), resource ('from Todoist'), and scope ('using the filter "#Waiting | #Brian waiting | #Ansonia Waiting"'), distinguishing it from sibling tools like get_tasks_due_today or get_tasks_with_label by focusing on a specific filter-based retrieval.

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

Usage Guidelines3/5

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

The description implies usage context by specifying the filter criteria, but does not explicitly state when to use this tool versus alternatives like search_tasks or get_tasks_with_label. It provides some guidance through the filter details but lacks explicit comparisons or exclusions.

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/bkotos/todoist-mcp'

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