Skip to main content
Glama
dragosroua

addTaskManager MCP Server

by dragosroua

get_tasks_overdue_in_do

Retrieve overdue tasks from the Do realm in the ADD framework to identify items requiring immediate completion.

Instructions

Find tasks overdue in Do realm.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'get_tasks_overdue_in_do'. Delegates to CloudKitService in production or returns mock overdue tasks. Formats response with task details, overdue days, context, and priority.
    private async getTasksOverdueInDo() {
      return this.withCloudKitOrMock(
        'getTasksOverdueInDo',
        async () => {
          // CloudKit production implementation
          const overdueTasks = await this.cloudKitService.getTasksInDoOverdue();
          
          let response = `Overdue items in Do realm (past due dates - need immediate attention):\n`;
          if (overdueTasks.length === 0) {
            response += 'No overdue tasks in Do realm! 🎉 Great job staying on track!';
          } else {
            response += overdueTasks.map((task: any) => {
              const name = task.fields?.taskName?.value || 'Unnamed Task';
              const contextRecordName = task.fields?.context?.value?.recordName;
              const contextName = contextRecordName?.replace('context_', '') || 'No context';
              const priority = task.fields?.taskPriority?.value || 3;
              const priorityIcon = priority === 1 ? '🔴 High' : priority === 2 ? '🟡 Medium' : '🟢 Low';
              const endDate = task.fields?.endDate?.value;
              const overdueDays = Math.ceil((Date.now() - new Date(endDate).getTime()) / (24 * 60 * 60 * 1000));
              const urgency = overdueDays > 3 ? '⚠️ URGENT' : '❗ Overdue';
              
              return `- ${urgency} ${name} (${task.recordName}) - ${overdueDays} day${overdueDays > 1 ? 's' : ''} overdue - ${contextName} - ${priorityIcon}`;
            }).join('\n');
          }
          
          return { content: [{ type: 'text', text: response }] };
        },
        async () => {
          // Mock implementation
          const now = new Date();
          const yesterday = new Date(now.getTime() - 86400000);
          const weekAgo = new Date(now.getTime() - 7 * 86400000);
          
          const mockTasks = [
            { 
              recordName: 'task_overdue_1', 
              taskName: 'Submit expense report', 
              realmId: 3, 
              endDate: yesterday.toISOString().split('T')[0],
              contextRecordName: 'context_work',
              priority: 1,
              daysOverdue: 1
            },
            { 
              recordName: 'project_overdue_1', 
              projectName: 'Clean garage', 
              realmId: 3, 
              endDate: weekAgo.toISOString().split('T')[0],
              contextRecordName: 'context_home',
              priority: 3,
              daysOverdue: 7
            }
          ];
          
          let response = `Overdue items in Do realm (past due dates - need immediate attention):\n`;
          response += mockTasks.map(item => {
            const type = item.recordName.startsWith('task_') ? 'Task' : 'Project';
            const name = item.taskName || (item as any).projectName;
            const contextName = item.contextRecordName?.replace('context_', '') || 'No context';
            const priority = item.priority === 1 ? '🔴 High' : item.priority === 2 ? '🟡 Medium' : '🟢 Low';
            const overdueDays = item.daysOverdue;
            const urgency = overdueDays > 3 ? '⚠️ URGENT' : '❗ Overdue';
            return `- ${urgency} ${name} (${item.recordName}) - ${overdueDays} day${overdueDays > 1 ? 's' : ''} overdue - ${contextName} - ${priority}`;
          }).join('\n');
          
          return { content: [{ type: 'text', text: response }] };
        }
      );
    }
  • Core implementation: CloudKit query for Tasks in Do realm (realmId=3) with endDate < now, sorted by endDate ascending (most overdue first).
    async getTasksInDoOverdue(): Promise<ZenTaskticTask[]> {
      const now = new Date().getTime();
      
      return this.queryRecords<ZenTaskticTask>('Task', {
        filterBy: [
          { fieldName: 'realmId', fieldValue: 3, comparator: 'EQUALS' },
          { fieldName: 'endDate', fieldValue: now, comparator: 'LESS_THAN' }
        ],
        sortBy: [{ fieldName: 'endDate', ascending: true }] // Most overdue first
      });
    }
  • src/index.ts:775-776 (registration)
    Tool registration in CallToolRequestSchema switch statement, dispatching to handler.
    return await this.getTasksOverdueInDo();
  • src/index.ts:634-637 (registration)
    Tool registration/declaration in ListToolsRequestSchema response, including schema (no input params).
      name: 'get_tasks_overdue_in_do',
      description: 'Find tasks overdue in Do realm.',
      inputSchema: { type: 'object', properties: {} }
    }
  • Input schema for the tool: empty object (no parameters required).
    }
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. It states 'Find tasks overdue in Do realm', implying a read-only query, but doesn't disclose behavioral traits such as authentication requirements, rate limits, return format, pagination, or what constitutes 'overdue'. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 with no wasted words. It's front-loaded with the core purpose, making it easy to parse quickly. Every word earns its place by specifying the action and target.

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

Completeness2/5

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

Given the tool's complexity (a query with no parameters but likely returning task data), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what 'overdue' means, the return format, or any constraints, leaving the agent with insufficient context to use the tool effectively.

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 with 100% schema description coverage, so the schema fully documents the lack of inputs. The description doesn't need to add parameter semantics, and it doesn't contradict the schema. Baseline is 4 for 0 parameters, as the description appropriately doesn't discuss 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 'Find tasks overdue in Do realm' clearly states the action (find) and resource (tasks overdue in Do realm). It distinguishes from siblings like 'get_tasks_by_realm' or 'get_tasks_today_in_do' by specifying 'overdue' and 'Do realm', but doesn't explicitly contrast with similar tools like 'get_tasks_soon_in_do' or 'get_tasks_today_in_do' beyond the 'overdue' qualifier.

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 prerequisites, exclusions, or compare with siblings like 'get_tasks_by_realm' or 'get_tasks_today_in_do', leaving the agent to infer usage based on the name alone.

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