Skip to main content
Glama

things_get_todo_details

Retrieve comprehensive details for a specific to-do item, including deadline, notes, and current status, to manage tasks effectively within the Things 3 app.

Instructions

Get detailed information about a specific to-do including deadline, notes, status, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the to-do to get detailed information for

Implementation Reference

  • The execute function in GetToolHandler handles the logic for executing AppleScripts, including the 'things_get_todo_details' tool, mapping it to the 'get-todo-details' script and parsing the output using 'parseTodoDetails'.
    async execute(toolName: string, params: GetParams): Promise<string> {
      let scriptName: string;
      
      // Handle the get_list tool separately
      if (toolName === 'things_get_list') {
        const listParams = params as z.infer<typeof GetListByNameSchema>;
        scriptName = this.listNameToScript[listParams.list];
        if (!scriptName) {
          throw new Error(`Unknown list: ${listParams.list}`);
        }
      } else {
        scriptName = this.scriptMap[toolName];
        if (!scriptName) {
          throw new Error(`Unknown tool: ${toolName}`);
        }
      }
      
      let scriptArgs: string[] = [];
      const options = { maxResults: (params as any).max_results };
      
      // Handle specific tools that need arguments
      if (toolName === 'things_get_project') {
        const projectParams = params as z.infer<typeof GetProjectSchema>;
        scriptArgs = [projectParams.project_id];
      } else if (toolName === 'things_get_area') {
        const areaParams = params as z.infer<typeof GetAreaSchema>;
        scriptArgs = [areaParams.area_id];
      } else if (toolName === 'things_get_todo_details') {
        const todoParams = params as z.infer<typeof GetTodoDetailsSchema>;
        scriptArgs = [todoParams.id];
        // Don't pass maxResults for todo details since it's a single item
        delete options.maxResults;
      }
      
      const output = await executeAppleScriptFile(scriptName, scriptArgs, options);
      
      // Return empty array for empty output
      if (!output.trim()) {
        const emptyResult = toolName.includes('project') || toolName.includes('area') 
          ? { todos: [] }
          : { [this.getResultKey(toolName)]: [] };
        return JSON.stringify(emptyResult, null, 2);
      }
      
      // Parse based on tool type
      let result;
      switch (toolName) {
        case 'things_get_projects':
          result = { projects: parseProjectList(output) };
          break;
        case 'things_get_areas':
          result = { areas: parseAreaList(output) };
          break;
        case 'things_get_tags':
          result = { tags: parseTagList(output) };
          break;
        case 'things_get_todo_details':
          result = parseTodoDetails(output);
          break;
        default:
          result = { todos: parseTodoList(output) };
      }
      
      return JSON.stringify(result, null, 2);
    }
  • src/tools/get.ts:77-80 (registration)
    The 'things_get_todo_details' tool definition including its schema registration within the GetToolHandler class.
      name: 'things_get_todo_details',
      description: 'Get detailed information about a specific to-do including deadline, notes, status, etc.',
      schema: GetTodoDetailsSchema
    }
  • The input schema for 'things_get_todo_details' imported from '../types/mcp.js'.
    import { GetProjectSchema, GetAreaSchema, GetListSchema, GetListByNameSchema, GetTodoDetailsSchema } from '../types/mcp.js';
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 adds value by disclosing returned fields (deadline, notes, status, etc.), hinting at output structure since no output schema exists. However, it omits other behavioral traits like error handling (404 if not found), read-only safety, or side effects.

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

Conciseness4/5

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

Single sentence, front-loaded with the action verb. Efficient structure with minimal waste, though 'etc.' is slightly vague regarding additional returned fields. Appropriately concise for the tool's simplicity.

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 single-parameter read operation with no annotations, the description is adequate but has gaps. It partially compensates for the missing output schema by listing example fields, though it could clarify that it returns a single object versus a collection.

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

Parameters3/5

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

Input schema has 100% description coverage for the single 'id' parameter. The description does not mention parameters explicitly, but with complete schema documentation, the baseline score of 3 is appropriate as the schema sufficiently carries the semantic load.

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?

Uses specific verb 'Get' with clear resource 'detailed information about a specific to-do'. The phrase 'specific to-do' effectively distinguishes this from sibling list operations (things_get_today, things_get_inbox) and mutation operations (things_update_todo, things_add_todo).

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 phrase 'specific to-do' implies usage when an ID is known versus listing operations, but lacks explicit guidance on when to use this versus list views or prerequisite steps (e.g., obtaining an ID first). No explicit alternatives or exclusions 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/hildersantos/things-mcp'

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