Skip to main content
Glama
dragosroua

addTaskManager MCP Server

by dragosroua

decide_move_task_to_do

Move tasks from the Decide realm to the Do realm to mark them ready for execution in the ADD framework workflow.

Instructions

Move task to Do realm from Decide realm.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskRecordNameYesTask record name

Implementation Reference

  • src/index.ts:477-487 (registration)
    Tool registration in ListToolsRequestSchema handler, including name, description, and input schema.
    {
      name: 'decide_move_task_to_do',
      description: 'Move task to Do realm from Decide realm.',
      inputSchema: {
        type: 'object',
        properties: {
          taskRecordName: { type: 'string', description: 'Task record name' }
        },
        required: ['taskRecordName']
      }
    },
  • Dispatch handler in CallToolRequestSchema switch statement: validates input arguments and invokes the moveTaskToRealm method.
    case 'decide_move_task_to_do':
      this.validateArgs(args, ['taskRecordName']);
      return await this.moveTaskToRealm(args.taskRecordName, 'do');
  • Primary handler function for moving tasks between realms: performs realm transition validation and delegates to moveItemToRealm.
    private async moveTaskToRealm(taskRecordName: string, targetRealm: string) {
      // Add validation before moving
      const validationResult = await this.validateRealmTransition(taskRecordName, 'Task', targetRealm as RealmString);
      if (!validationResult.valid) {
        throw new McpError(ErrorCode.InvalidParams, validationResult.reason);
      }
      return this.moveItemToRealm(taskRecordName, 'Task', targetRealm as RealmString);
    }
  • Helper function that performs the actual realm move: updates realmId, applies ADD framework cleanup rules, and returns success message (mock implementation).
    private async moveItemToRealm(itemRecordName: string, itemType: 'Task' | 'Project', targetRealmStr: RealmString) {
      const targetRealmId = realmStringToId(targetRealmStr);
      
      // Mock update realmId and clean up fields based on realm rules
      let updateMessage = `${itemType} ${itemRecordName} moved to ${targetRealmStr} realm (ID: ${targetRealmId})`;
      
      // Apply realm-specific cleanup rules
      if (targetRealmId === REALM_ASSESS_ID) {
        updateMessage += '. Context and due date cleared for fresh evaluation';
      } else if (targetRealmId === REALM_DECIDE_ID && targetRealmStr !== 'decide') {
        updateMessage += '. Ready for context assignment and due date setting';
      }
      
      return { content: [{ type: 'text', text: updateMessage }] };
    }
  • Helper function for realm transition validation according to ADD framework rules (Assess-Decide-Do), fetches item and checks allowed moves.
    private async validateRealmTransition(itemRecordName: string, itemType: 'Task' | 'Project', targetRealm: RealmString): Promise<{valid: boolean, reason: string}> {
      // Mock fetch current item data
      const currentItem = await this.mockFetchItem(itemRecordName, itemType);
      
      if (!currentItem) {
        return { valid: false, reason: `${itemType} ${itemRecordName} not found` };
      }
    
      const currentRealmId = currentItem.realmId;
      const targetRealmId = realmStringToId(targetRealm);
      
      // Validate transition rules based on ADD framework
      switch (currentRealmId) {
        case REALM_ASSESS_ID: // From Assess (1)
          return this.validateFromAssess(currentItem, targetRealmId, itemType);
        
        case REALM_DECIDE_ID: // From Decide (2)
          return this.validateFromDecide(currentItem, targetRealmId, itemType);
        
        case REALM_DO_ID: // From Do (3)
          return this.validateFromDo(currentItem, targetRealmId, itemType);
        
        default:
          return { valid: false, reason: `Invalid current realm ID: ${currentRealmId}` };
      }
    }
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 performs a 'Move' operation, implying mutation, but does not disclose any behavioral traits such as permissions required, side effects (e.g., if the task's status changes), error conditions, or what happens if the task is already in the Do realm. This is a significant gap for a mutation tool.

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 action ('Move task to Do realm from Decide realm') with zero wasted words. It is appropriately sized for the tool's simplicity.

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 mutation nature, lack of annotations, and no output schema, the description is incomplete. It does not address behavioral aspects like success/failure responses, error handling, or system state changes, which are critical for an agent to use the tool effectively in a workflow with other realm-management tools.

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?

The input schema has 100% description coverage, with 'taskRecordName' documented as 'Task record name'. The description does not add any meaning beyond this, such as explaining what constitutes a valid record name or format. Since schema coverage is high, the baseline score of 3 is appropriate.

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 ('Move') and the resource ('task'), specifying the direction from 'Decide realm' to 'Do realm'. It distinguishes this tool from other realm-moving tools like 'decide_move_project_to_do' by focusing on tasks, but does not explicitly differentiate from 'moveToRealm' or other task-moving siblings like 'decide_move_task_to_assess_from_decide'.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites (e.g., tasks must be in the Decide realm), exclusions, or compare to similar tools like 'moveToRealm' or 'decide_move_task_to_assess_from_decide', leaving the agent to infer usage from context 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