Skip to main content
Glama
dragosroua

addTaskManager MCP Server

by dragosroua

get_ready_items_in_decide

Retrieve tasks and projects ready for action in the Decide realm to manage workflow progression within the ADD framework.

Instructions

Find ready to do items (tasks + projects) in Decide realm.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Main handler function for the 'get_ready_items_in_decide' tool. Fetches ready tasks using CloudKitService.getTasksInDecideReady() and filters projects from Decide realm that have context and future due dates. Formats and returns the list of ready items.
    private async getReadyItemsInDecide() {
      return this.withCloudKitOrMock(
        'getReadyItemsInDecide',
        async () => {
          // CloudKit production implementation
          const [readyTasks, allProjects] = await Promise.all([
            this.cloudKitService.getTasksInDecideReady(),
            this.cloudKitService.getProjectsByRealm(2)
          ]);
    
          // Filter projects that have both context and future due date
          const now = new Date();
          const readyProjects = allProjects.filter((project: any) => {
            const hasContext = project.fields?.context?.value?.recordName;
            const endDate = project.fields?.endDate?.value;
            const hasFutureEndDate = endDate && new Date(endDate) > now;
            return hasContext && hasFutureEndDate;
          });
    
          const allReadyItems = [...readyTasks, ...readyProjects];
          
          let response = `Ready items in Decide realm (context + future due date set):\n`;
          if (allReadyItems.length === 0) {
            response += 'No items are ready for Do realm. Check undecided and stalled items first! 📋';
          } else {
            response += allReadyItems.map(item => {
              const isTask = item.recordType === 'Task';
              const name = isTask ? item.fields?.taskName?.value : item.fields?.projectName?.value;
              const contextRecordName = item.fields?.context?.value?.recordName;
              const endDate = item.fields?.endDate?.value;
              const type = isTask ? 'Task' : 'Project';
              
              const dueDate = new Date(endDate).toLocaleDateString();
              const contextName = contextRecordName?.replace('context_', '') || 'Unknown';
              
              return `- ${name} (${item.recordName}) - Due: ${dueDate}, Context: ${contextName} [${type}]`;
            }).join('\n');
          }
          
          return { content: [{ type: 'text', text: response }] };
        },
        async () => {
          // Mock implementation
          const tomorrow = new Date(Date.now() + 86400000).toISOString();
          const nextWeek = new Date(Date.now() + 7 * 86400000).toISOString();
          
          const mockItems = [
            { 
              recordName: 'task_ready_1', 
              taskName: 'Schedule dentist appointment',
              contextRecordName: 'context_personal',
              endDate: tomorrow,
              realmId: 2,
              readyStatus: 'Fully planned - ready for Do realm'
            },
            { 
              recordName: 'task_ready_2', 
              taskName: 'Submit expense report',
              contextRecordName: 'context_work',
              endDate: nextWeek,
              realmId: 2,
              readyStatus: 'Context and deadline set'
            },
            { 
              recordName: 'project_ready_1', 
              projectName: 'Plan weekend camping trip',
              contextRecordName: 'context_personal',
              endDate: nextWeek,
              realmId: 2,
              readyStatus: 'Timeline and context decided'
            }
          ];
          
          let response = `Ready items in Decide realm (context + future due date set):\n`;
          response += mockItems.map(item => {
            const type = item.recordName.startsWith('task_') ? 'Task' : 'Project';
            const name = item.taskName || (item as any).projectName;
            const dueDate = new Date(item.endDate).toLocaleDateString();
            const contextName = item.contextRecordName?.replace('context_', '') || 'Unknown';
            return `- ${name} (${item.recordName}) - Due: ${dueDate}, Context: ${contextName}`;
          }).join('\n');
          
          return { content: [{ type: 'text', text: response }] };
        }
      );
    }
  • src/index.ts:614-617 (registration)
    Tool registration in the ListToolsRequestSchema handler, including name, description, and input schema (no parameters required).
      name: 'get_ready_items_in_decide',
      description: 'Find ready to do items (tasks + projects) in Decide realm.',
      inputSchema: { type: 'object', properties: {} }
    },
  • Dispatch handler in the CallToolRequestSchema switch statement that invokes the main getReadyItemsInDecide method.
    case 'get_ready_items_in_decide':
      return await this.getReadyItemsInDecide();
  • Core helper method that queries CloudKit for tasks in Decide realm (realmId=2) with future endDate, then filters client-side for those with assigned context. Used by the main handler for tasks.
    async getTasksInDecideReady(): Promise<ZenTaskticTask[]> {
      const now = new Date().getTime();
      
      // Get tasks with future due dates first
      const tasksWithFutureDates = await this.queryRecords<ZenTaskticTask>('Task', {
        filterBy: [
          { fieldName: 'realmId', fieldValue: 2, comparator: 'EQUALS' },
          { fieldName: 'endDate', fieldValue: now, comparator: 'GREATER_THAN' }
        ]
      });
    
      // Filter client-side for those that also have a context
      return tasksWithFutureDates.filter((task: any) => 
        task.fields?.contextRecordName?.value != null
      );
    }
  • Helper method to fetch all projects in a given realm. Used by main handler to get Decide projects (realmId=2) then filter client-side for ready ones.
    async getProjectsByRealm(realmId: number): Promise<ZenTaskticProject[]> {
      return this.queryRecords<ZenTaskticProject>('Projects', {
        filterBy: [{ 
          fieldName: 'realmId', 
          fieldValue: realmId,
          comparator: 'EQUALS' 
        }],
        sortBy: [{ fieldName: 'lastModified', ascending: false }]
      });
    }
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. It states the tool finds items but doesn't describe what 'ready to do' means, how results are returned (e.g., format, pagination), or any operational constraints (e.g., permissions, rate limits). This leaves significant gaps in understanding the tool's behavior.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is appropriately sized for a simple tool with no parameters, though it could be slightly more structured by front-loading key terms like 'Find ready items' more explicitly.

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 output schema, no annotations), the description is minimally adequate but incomplete. It lacks details on what 'ready to do' entails, how results are structured, and differentiation from siblings, making it functional but not fully informative for an AI agent in a complex toolset.

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 schema description coverage is 100%, so there are no parameters to document. The description appropriately doesn't discuss parameters, which is correct for this case, earning a baseline score of 4 as it doesn't need to compensate for any schema gaps.

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 ('ready to do items (tasks + projects) in Decide realm'), which is specific and informative. However, it doesn't explicitly distinguish this tool from sibling tools like 'get_stalled_items_in_decide' or 'get_undecided_items_in_decide', which reduces its differentiation value.

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 this tool is appropriate, what prerequisites might exist, or how it differs from similar sibling tools like 'get_stalled_items_in_decide' or 'get_undecided_items_in_decide', leaving usage context unclear.

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