Skip to main content
Glama

get_chores_due_today

Retrieve today's or overdue chores from Todoist with structured details like content, due dates, and labels using a specific filter.

Instructions

Get all chores due today or overdue from Todoist using the filter "(today | overdue) & ##Chores". Returns structured JSON data with chore details including id, content, due date, project_id, and labels.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The complete tool definition for 'get_chores_due_today', including schema and the handler function that calls the helper getChoresDueToday() and returns the result as JSON text content.
    export const getChoresDueTodayTool: Tool = {
      schema: {
        name: 'get_chores_due_today',
        description:
          'Get all chores due today or overdue from Todoist using the filter "(today | overdue) & ##Chores". Returns structured JSON data with chore details including id, content, due date, project_id, and labels.',
        inputSchema: {
          type: 'object',
          properties: {},
          required: [],
        },
      },
      handler: async () => {
        console.error('Executing get_chores_due_today...');
        const result = await getChoresDueToday();
        console.error('get_chores_due_today completed successfully');
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      },
    };
  • The schema definition for the get_chores_due_today tool, specifying name, description, and empty input schema.
    schema: {
      name: 'get_chores_due_today',
      description:
        'Get all chores due today or overdue from Todoist using the filter "(today | overdue) & ##Chores". Returns structured JSON data with chore details including id, content, due date, project_id, and labels.',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
  • The helper function getChoresDueToday that fetches chores due today or overdue from Todoist using a specific filter and the shared fetchRawTasksByFilter utility.
    export async function getChoresDueToday(): Promise<TodoistTask[]> {
      return await fetchRawTasksByFilter(
        '(today | overdue) & ##Chores',
        'get chores due today'
      );
    }
  • Registration of the get_chores_due_today handler in the toolsWithoutArgs registry used by handleToolRequest.
    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,
    };
  • src/index.ts:102-103 (registration)
    Registration of the tool schema in the list of tools returned by ListToolsRequestHandler.
    searchTasksUsingOrTool.schema,
    getChoresDueTodayTool.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 describes the operation (fetching data), the source (Todoist), the filter logic, and the return format. However, it doesn't mention potential limitations like rate limits, authentication requirements, error conditions, or whether the data is cached/live. For a read-only tool with zero annotation coverage, this is adequate but leaves gaps.

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 purpose, filter logic, and return format without any wasted words. It's front-loaded with the core action and resource, making it easy to parse.

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 complexity (simple read operation with no parameters), lack of annotations, and no output schema, the description does a good job of explaining what it does, how it works (via the filter), and what it returns. However, without an output schema, it could benefit from more detail on the exact structure of the 'chore details' (e.g., field types or examples), though the listed fields (id, content, etc.) provide reasonable coverage.

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 schema already fully documents the lack of inputs. The description adds value by explaining that no parameters are needed because it uses a hardcoded filter ('(today | overdue) & ##Chores') and specifies the data source (Todoist), which isn't in the schema. This compensates well for the parameter-less design.

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 chores due today or overdue'), identifies the resource ('from Todoist'), and distinguishes itself from siblings by specifying the exact filter used ('(today | overdue) & ##Chores') and the type of data returned ('structured JSON data with chore details'). This goes beyond just restating the tool name.

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

Usage Guidelines4/5

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

The description provides clear context about when to use this tool (for chores due today or overdue with a specific Todoist filter), but it doesn't explicitly mention when not to use it or name specific alternatives among the many sibling tools. The implicit alternative would be other task-fetching tools like 'get_tasks_due_tomorrow' or 'get_tasks_due_this_week', but this isn't stated.

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