Skip to main content
Glama
dragosroua

addTaskManager MCP Server

by dragosroua

get_undecided_items_in_decide

Identify tasks and projects awaiting decisions in the Decide realm to facilitate assignment of contexts and dates for the ADD framework workflow.

Instructions

Find undecided items (tasks + projects) in Decide realm.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:608-612 (registration)
    Tool registration entry defining the name, description, and input schema (empty object) for listTools response.
    {
      name: 'get_undecided_items_in_decide',
      description: 'Find undecided items (tasks + projects) in Decide realm.',
      inputSchema: { type: 'object', properties: {} }
    },
  • Dispatch handler in CallToolRequestSchema switch statement calling the main implementation method.
    return await this.getUndecidedItemsInDecide();
  • Primary handler function implementing tool logic: queries CloudKitService for undecided tasks in Decide realm, filters projects lacking context or due date, formats human-readable response. Falls back to mock in development.
    private async getUndecidedItemsInDecide() {
      return this.withCloudKitOrMock(
        'getUndecidedItemsInDecide',
        async () => {
          // CloudKit production implementation
          const [undecidedTasks, allProjects] = await Promise.all([
            this.cloudKitService.getTasksInDecideUndecided(),
            this.cloudKitService.getProjectsByRealm(2)
          ]);
    
          // Filter projects that lack context or due date
          const undecidedProjects = allProjects.filter((project: any) => {
            const hasContext = project.fields?.context?.value?.recordName;
            const hasEndDate = project.fields?.endDate?.value;
            return !hasContext || !hasEndDate;
          });
    
          const allUndecidedItems = [...undecidedTasks, ...undecidedProjects];
          
          let response = `Undecided items in Decide realm (need context/timeline decisions):\n`;
          if (allUndecidedItems.length === 0) {
            response += 'All items in Decide realm have context and due dates set! ✅';
          } else {
            response += allUndecidedItems.map(item => {
              const isTask = item.recordType === 'Task';
              const name = isTask ? item.fields?.taskName?.value : item.fields?.projectName?.value;
              const hasContext = item.fields?.context?.value?.recordName;
              const hasEndDate = item.fields?.endDate?.value;
              const type = isTask ? 'Task' : 'Project';
              
              const missing = [];
              if (!hasContext) missing.push('context');
              if (!hasEndDate) missing.push('due date');
              
              return `- ${name} (${item.recordName}) - needs: ${missing.join(' + ')} [${type}]`;
            }).join('\n');
          }
          
          return { content: [{ type: 'text', text: response }] };
        },
        async () => {
          // Mock implementation
          const mockItems = [
            { 
              recordName: 'task_undecided_1', 
              taskName: 'Research new marketing strategy',
              contextRecordName: null,
              endDate: null,
              realmId: 2,
              needsDecision: 'Context and timeline'
            },
            { 
              recordName: 'task_undecided_2', 
              taskName: 'Call insurance company',
              contextRecordName: 'context_home',
              endDate: null,
              realmId: 2,
              needsDecision: 'Due date scheduling'
            },
            { 
              recordName: 'project_undecided_1', 
              projectName: 'Organize home office',
              contextRecordName: null,
              endDate: null,
              realmId: 2,
              needsDecision: 'Context and timeline'
            }
          ];
          
          let response = `Undecided items in Decide realm (need context/timeline decisions):\n`;
          response += mockItems.map(item => {
            const type = item.recordName.startsWith('task_') ? 'Task' : 'Project';
            const name = item.taskName || (item as any).projectName;
            const missing = [];
            if (!item.contextRecordName) missing.push('context');
            if (!item.endDate) missing.push('due date');
            return `- ${name} (${item.recordName}) - needs: ${missing.join(' + ')}`;
          }).join('\n');
          
          return { content: [{ type: 'text', text: response }] };
        }
      );
  • Core helper method fetching undecided tasks (no context OR no endDate) in Decide realm (realmId=2) via two CloudKit queries (OR not natively supported) + deduplication.
    async getTasksInDecideUndecided(): Promise<ZenTaskticTask[]> {
      // CloudKit doesn't support complex OR conditions directly
      // We'll need to make two queries and combine results
      
      const [noContext, noDueDate] = await Promise.all([
        // Tasks with no context
        this.queryRecords<ZenTaskticTask>('Task', {
          filterBy: [
            { fieldName: 'realmId', fieldValue: 2, comparator: 'EQUALS' },
            { fieldName: 'contextRecordName', fieldValue: null, comparator: 'EQUALS' }
          ]
        }),
        // Tasks with no due date  
        this.queryRecords<ZenTaskticTask>('Task', {
          filterBy: [
            { fieldName: 'realmId', fieldValue: 2, comparator: 'EQUALS' },
            { fieldName: 'endDate', fieldValue: null, comparator: 'EQUALS' }
          ]
        })
      ]);
    
      // Combine and deduplicate by recordName
      const combined = [...noContext, ...noDueDate];
      const uniqueRecords = new Map();
      combined.forEach(task => {
        uniqueRecords.set((task as any).recordName, task);
      });
    
      return Array.from(uniqueRecords.values());
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'finds' items, implying a read-only operation, but doesn't clarify aspects like whether it requires authentication, how results are returned (e.g., pagination, format), or any rate limits. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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, efficient sentence that front-loads the core purpose without any wasted words. It directly conveys what the tool does in a clear and structured manner, making it easy to parse and understand quickly.

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 simplicity (0 parameters, no annotations, no output schema), the description is adequate as a minimum viable explanation. It specifies the resource type and realm, but lacks details on return values, authentication needs, or behavioral traits. For a read operation with no structured output schema, more context on what is returned would be beneficial, but it's not critically incomplete.

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 tool has 0 parameters, and the input schema has 100% description coverage (though empty). With no parameters to document, the description doesn't need to add parameter semantics beyond what the schema provides. A baseline score of 4 is appropriate as it avoids redundancy while clearly indicating the tool operates without inputs.

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 action ('Find') and the target resources ('undecided items (tasks + projects) in Decide realm'), which provides a specific verb+resource combination. However, it doesn't explicitly distinguish this tool from sibling tools like 'get_ready_items_in_decide' or 'get_stalled_items_in_decide', which also retrieve items from the Decide realm with different filters.

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. It doesn't mention when to choose it over sibling tools like 'get_ready_items_in_decide' or 'get_stalled_items_in_decide', nor does it specify any prerequisites or exclusions for its use.

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/dragosroua/addtaskmanager-mcp-server'

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