Skip to main content
Glama

get_areas_of_focus

Retrieve all tasks from the Todoist "Areas of focus" project to view structured task details including content, priority, due dates, and labels.

Instructions

Get all tasks from the "Areas of focus" project in Todoist. Returns structured JSON data with task details including id, content, description, priority, due date, labels, and more.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The primary handler implementation for the 'get_areas_of_focus' tool. It invokes getAreasOfFocus() from task-retrieval service and formats the result as JSON text content block.
    export const getAreasOfFocusTool: Tool = {
      schema: {
        name: 'get_areas_of_focus',
        description:
          'Get all tasks from the "Areas of focus" project in Todoist. Returns structured JSON data with task details including id, content, description, priority, due date, labels, and more.',
        inputSchema: {
          type: 'object',
          properties: {},
          required: [],
        },
      },
      handler: async () => {
        console.error('Executing get_areas_of_focus...');
        const result = await getAreasOfFocus();
        console.error('get_areas_of_focus completed successfully');
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      },
    };
  • Tool schema defining name, description, and empty input schema (no parameters required).
    schema: {
      name: 'get_areas_of_focus',
      description:
        'Get all tasks from the "Areas of focus" project in Todoist. Returns structured JSON data with task details including id, content, description, priority, due date, labels, and more.',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
  • Core helper function that retrieves tasks from the 'Areas of focus' Todoist project using a filter query and transforms them into structured TasksResponse.
    export async function getAreasOfFocus(): Promise<TasksResponse> {
      return await fetchTasksByFilter(
        `##${ProjectNames.AREAS_OF_FOCUS}`,
        'get tasks from Areas of focus project'
      );
    }
  • Registers the 'get_areas_of_focus' handler in the toolsWithoutArgs registry for execution dispatching.
    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 MCP server's listTools handler for tool discovery.
    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,
        ],
      };
Behavior2/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 mentions the return format ('structured JSON data') and some fields, but lacks details on permissions, rate limits, pagination, or error handling. For a read operation with zero annotation coverage, this leaves significant behavioral 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 two sentences: the first states the purpose and source, the second details the return data. It's front-loaded with the core function and efficiently lists key fields without redundancy. Every sentence adds value.

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

Completeness3/5

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

For a read-only tool with 0 parameters and no output schema, the description covers the purpose and return format adequately. However, without annotations or output schema, it lacks details on response structure (e.g., array format) and behavioral constraints, making it minimally complete.

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 doesn't discuss parameters, earning a baseline score of 4 for not adding unnecessary information.

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 verb 'Get' and the resource 'tasks from the Areas of focus project in Todoist', specifying the source and type of data. It distinguishes from siblings by targeting a specific project rather than general task retrieval, though it doesn't explicitly name alternatives like 'get_tasks_due_this_week'.

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 when tasks from the 'Areas of focus' project are needed, but doesn't provide explicit guidance on when to use this tool versus other task-retrieval siblings (e.g., 'get_tasks_due_tomorrow' or 'search_tasks'). No exclusions or prerequisites are mentioned.

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