Skip to main content
Glama

things_get_someday

Retrieve all tasks marked for future consideration in the Someday list, with optional result limits for focused planning.

Instructions

Get all to-dos in Someday

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_resultsNoLimit number of results returned (defaults to all if not specified)

Implementation Reference

  • The `execute` method in `GetToolHandler` handles the logic for the 'things_get_someday' tool by mapping it to the 'get-someday' AppleScript and executing it.
    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:31-35 (registration)
    The 'things_get_someday' tool is defined within the `definitions` array of `GetToolHandler`.
    {
      name: 'things_get_someday',
      description: 'Get all to-dos in Someday',
      schema: GetListSchema
    },
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 of behavioral disclosure. While 'Get' implies a read-only operation, the description confirms nothing about safety, rate limits, or the return structure. It also does not clarify whether 'Someday' is a static list or dynamic query, or what fields are returned for each to-do.

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?

The description is extremely concise at five words with no redundant or wasted content. However, it may be overly terse—lacking even a single sentence of context about the 'Someday' list concept—suggesting it could benefit from slightly more length to improve clarity without sacrificing efficiency.

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?

Given the tool's low complexity (one optional parameter, no nested objects, no output schema), the description is minimally sufficient. It identifies the target resource, but for a tool returning unknown data structures without an output schema, it should ideally describe what constitutes a 'Someday' to-do or what data is returned.

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?

Schema description coverage is 100%, establishing a baseline of 3. The description mentions 'all' to-dos, which aligns with the max_results parameter's default behavior (returns all if not specified), but adds no additional semantic context about parameter usage, validation rules, or pagination behavior beyond what the schema already provides.

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 uses a clear verb ('Get') and specifies the exact resource ('to-dos in Someday'). It effectively distinguishes from siblings like things_get_today or things_get_inbox by naming the specific 'Someday' list. However, it assumes familiarity with the Things app taxonomy without clarifying what 'Someday' represents.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like things_get_anytime, things_get_upcoming, or things_get_today. It does not indicate whether Someday items are excluded from other lists or when this specific view is appropriate.

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