Skip to main content
Glama

get-todos

Retrieve tasks from Things 3 with filters for projects, lists, areas, status, and search queries to organize your workflow.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_uuidNoOptional UUID of a specific project
include_itemsNoInclude checklist items
listNoBuilt-in list name like Inbox, Today, Anytime
areaNoOptional area UUID or title filter
statusNoOptional status filter
queryNoOptional title/notes search
detailNoResponse detail level. Defaults to compact.
limitNoMaximum number of todos to return

Implementation Reference

  • The "get-todos" MCP tool is registered and implemented in src/index.ts. It filters tasks from the Things 3 database based on optional parameters like project, list (built-in lists), area, status, and query, and returns them formatted as a task view.
      "get-todos",
      {
        project_uuid: z.string().optional().describe("Optional UUID of a specific project"),
        include_items: z.boolean().optional().describe("Include checklist items"),
        list: z.string().optional().describe("Built-in list name like Inbox, Today, Anytime"),
        area: z.string().optional().describe("Optional area UUID or title filter"),
        status: z.string().optional().describe("Optional status filter"),
        query: z.string().optional().describe("Optional title/notes search"),
        detail: z.enum(["compact", "full"]).optional().describe("Response detail level. Defaults to compact."),
        limit: z.number().int().positive().optional().describe("Maximum number of todos to return"),
      },
      async ({ project_uuid, include_items, list, area, status, query, detail, limit }) => {
        const requestedDetail = detail ?? "compact";
        const todos = await withDatabase((db) => {
          const tasks = getAllTasks(db);
          let result = tasks.filter((task) => task.type === "to-do" && !task.trashed);
    
          if (project_uuid) {
            result = result.filter((task) => task.projectId === project_uuid);
          }
    
          if (list) {
            const normalized = list.toLowerCase();
            if (normalized === "inbox") result = getInboxTodos(tasks);
            if (normalized === "today") result = getTodayTodos(tasks);
            if (normalized === "upcoming") result = getUpcomingTodos(tasks);
            if (normalized === "anytime") result = getAnytimeTodos(tasks);
            if (normalized === "someday") result = getSomedayTodos(tasks);
            if (normalized === "logbook") result = getLogbookTodos(tasks);
            if (normalized === "trash") result = getTrashItems(tasks).filter((task) => task.type === "to-do");
          }
    
          if (area) {
            const lower = area.toLowerCase();
            result = result.filter(
              (task) =>
                task.areaId?.toLowerCase() === lower ||
                task.areaTitle?.toLowerCase() === lower
            );
          }
    
          if (status) {
            result = result.filter((task) => task.status === status.toLowerCase());
          }
    
          if (query) {
            result = result.filter((task) => matchesQuery(task, query));
          }
    
          result = applyLimit(result, limit);
          return result.map((task) =>
            toTaskView(task, requestedDetail, {
              includeChecklist: include_items !== false,
            })
          );
        });
    
        return buildTextResponse(`Found ${todos.length} todos`, {
          todos,
          detail: requestedDetail,
          limit: limit ?? null,
        });
      }
    );
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/soycanopa/SupaThings-MCP'

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