Skip to main content
Glama

get_tasks_due_tomorrow

Retrieve tasks due tomorrow from Todoist, filtering out specific project categories like Tickler and Chores. Returns structured JSON with task details including content, due date, and labels.

Instructions

Get all tasks due tomorrow from Todoist, excluding various project categories like Tickler, Chores, and baby-related projects. Returns structured JSON data with task details including id, content, due date, project id, and labels.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP Tool definition including the handler function that executes the tool logic by calling getTasksDueTomorrow() and formatting the result as JSON text content.
    export const getTasksDueTomorrowTool: Tool = {
      schema: {
        name: 'get_tasks_due_tomorrow',
        description:
          'Get all tasks due tomorrow from Todoist, excluding various project categories like Tickler, Chores, and baby-related projects. Returns structured JSON data with task details including id, content, due date, project id, and labels.',
        inputSchema: {
          type: 'object',
          properties: {},
          required: [],
        },
      },
      handler: async () => {
        console.error('Executing get_tasks_due_tomorrow...');
        const result = await getTasksDueTomorrow();
        console.error('get_tasks_due_tomorrow completed successfully');
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      },
    };
  • Input schema definition for the get_tasks_due_tomorrow tool (no input parameters required).
    schema: {
      name: 'get_tasks_due_tomorrow',
      description:
        'Get all tasks due tomorrow from Todoist, excluding various project categories like Tickler, Chores, and baby-related projects. Returns structured JSON data with task details including id, content, due date, project id, and labels.',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
  • Registration of the get_tasks_due_tomorrow tool handler in the toolsWithoutArgs registry map used for handling tool calls.
    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 that fetches raw Todoist tasks due tomorrow using the predefined TOMORROW_FILTER and generic fetchRawTasksByFilter utility.
    export async function getTasksDueTomorrow(): Promise<TodoistTask[]> {
      return await fetchRawTasksByFilter(TOMORROW_FILTER, 'get tasks due tomorrow');
    }
  • src/index.ts:104-115 (registration)
    The tool schema is registered in the listTools response for MCP protocol compliance.
      getTasksDueTomorrowTool.schema,
      getTasksDueThisWeekTool.schema,
      getTicklerTasksTool.schema,
      listGtdProjectsTool.schema,
      getWaitingTasksTool.schema,
      getRecentMediaTool.schema,
      getAreasOfFocusTool.schema,
      getShoppingListTool.schema,
      completeBeckyTaskTool.schema,
      listBrianTimeSensitiveTasksTool.schema,
      listBeckyTimeSensitiveTasksTool.schema,
    ],
Behavior3/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 clearly describes the read-only nature ('Get all tasks') and the filtering behavior ('excluding various project categories'), which is helpful. However, it doesn't mention potential limitations like rate limits, authentication requirements, or error handling, leaving some behavioral aspects unspecified.

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, well-structured sentence that efficiently conveys the tool's purpose, exclusions, and return format. Every part earns its place: the action, source, filtering criteria, and output details are all essential and presented without redundancy or unnecessary elaboration.

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's simplicity (0 parameters, no annotations, no output schema), the description is quite complete. It explains what the tool does, what it excludes, and what it returns. However, without an output schema, it could benefit from more detail on the JSON structure (e.g., field types or examples), but the provided information is sufficient for basic understanding.

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 tool has 0 parameters with 100% schema description coverage, so the baseline is 4. The description adds no parameter information beyond the schema, but this is acceptable since there are no parameters to document. The description focuses on the tool's purpose and behavior instead.

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 tasks due tomorrow from Todoist') and resource ('tasks'), with explicit exclusions ('excluding various project categories like Tickler, Chores, and baby-related projects'). It distinguishes from siblings like 'get_tasks_due_this_week' by specifying the exact time frame (tomorrow) and filtering criteria.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool ('Get all tasks due tomorrow') and when not to use it ('excluding various project categories like Tickler, Chores, and baby-related projects'). It implicitly suggests alternatives like 'get_tasks_due_this_week' for different time frames or 'get_tasks_with_label' for label-based filtering, making it clear this is for a specific, filtered subset.

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