Skip to main content
Glama

list_becky_time_sensitive_tasks

Retrieve Becky's time-sensitive Todoist tasks filtered by ##Becky time sensitive (per BK) & !subtask criteria. Returns structured JSON with task details including content, due dates, priority, and completion status.

Instructions

List all Becky time sensitive tasks from Todoist using the ##Becky time sensitive \(per BK\) & !subtask filter. 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

  • Tool definition including schema and handler function that executes the logic by fetching Becky time sensitive tasks and returning formatted JSON.
    export const listBeckyTimeSensitiveTasksTool: Tool = {
      schema: {
        name: 'list_becky_time_sensitive_tasks',
        description: `List all Becky time sensitive tasks from Todoist using the ##${ProjectNames.BECKY_TIME_SENSITIVE} & !subtask filter. 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: [],
        },
      },
      handler: async () => {
        console.error('Executing list_becky_time_sensitive_tasks...');
        const result = await listBeckyTimeSensitiveTasks();
        console.error('list_becky_time_sensitive_tasks completed successfully');
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      },
    };
  • Core helper function that retrieves Becky time sensitive tasks from Todoist using a specific filter and transforms them into structured response.
    export async function listBeckyTimeSensitiveTasks(): Promise<TasksResponse> {
      return await fetchTasksByFilter(
        `##${ProjectNames.BECKY_TIME_SENSITIVE} & !subtask`,
        'list Becky time sensitive tasks'
      );
    }
  • Registers the tool handler in the dispatch registry for tools without arguments.
    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:79-116 (registration)
    Registers the tool schema in the list of available tools for the MCP server.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
          getTaskCommentsTool.schema,
          listPersonalInboxTasksTool.schema,
          listBrianInboxPerBeckyTasksTool.schema,
          listBeckyInboxPerBrianTasksTool.schema,
          listNextActionsTool.schema,
          getBrianOnlyProjectsTool.schema,
          getBrianSharedProjectsTool.schema,
          getBeckySharedProjectsTool.schema,
          getInboxProjectsTool.schema,
          createProjectLabelTool.schema,
          createTaskCommentTool.schema,
          updateTaskTool.schema,
          createTaskTool.schema,
          moveTaskTool.schema,
          getContextLabelsTool.schema,
          getTasksWithLabelTool.schema,
          completeTaskTool.schema,
          uncompleteTaskTool.schema,
          searchTasksTool.schema,
          searchTasksUsingAndTool.schema,
          searchTasksUsingOrTool.schema,
          getChoresDueTodayTool.schema,
          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. It discloses the return format ('structured JSON data with task details') and specific fields included, which is useful. However, it doesn't mention behavioral aspects like rate limits, authentication needs, pagination, or error handling, 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 a single, well-structured sentence that front-loads the purpose and includes essential details (filter criteria and return data) without any wasted words. Every part earns its place by adding value.

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 output schema, no annotations), the description is largely complete—it specifies what it lists, the filter, and the return format. However, it lacks details on behavioral traits (e.g., read-only nature, potential limits), which would enhance completeness for an agent.

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 doesn't add param info, which is fine here, but it could have noted the lack of parameters explicitly. Baseline is 4 for 0 params, as it's complete for this case.

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 verb 'List' and the specific resource 'Becky time sensitive tasks from Todoist', including the exact filter criteria '##Becky time sensitive (per BK) & !subtask'. It distinguishes from siblings like 'list_brian_time_sensitive_tasks' by specifying 'Becky' tasks and from general task listing tools by the time-sensitive filter.

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 implicitly indicates when to use this tool—when needing Becky's time-sensitive tasks excluding subtasks. However, it doesn't explicitly state when not to use it or name alternatives (e.g., 'list_brian_time_sensitive_tasks' for Brian's tasks), though the specificity helps infer usage context.

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