Skip to main content
Glama
dragosroua

addTaskManager MCP Server

by dragosroua

decide_move_task_to_assess_from_decide

Move a task from the Decide realm to the Assess realm for review and editing when priorities or details need adjustment before action.

Instructions

Move task to Assess realm from Decide realm.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskRecordNameYesTask record name

Implementation Reference

  • src/index.ts:488-498 (registration)
    Registration of the tool 'decide_move_task_to_assess_from_decide' in the listTools response, including name, description, and input schema definition.
    {
      name: 'decide_move_task_to_assess_from_decide',
      description: 'Move task to Assess realm from Decide realm.',
      inputSchema: {
        type: 'object',
        properties: {
          taskRecordName: { type: 'string', description: 'Task record name' }
        },
        required: ['taskRecordName']
      }
    },
  • Dispatch case in the CallToolRequestSchema handler that validates arguments and delegates to the moveTaskToRealm method.
    case 'decide_move_task_to_assess_from_decide':
      this.validateArgs(args, ['taskRecordName']);
      return await this.moveTaskToRealm(args.taskRecordName, 'assess');
  • Core handler function for moving tasks between realms. Validates the realm transition according to ADD framework rules before executing the move.
    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 operation, applies realm-specific rules (e.g., clearing context/due dates when moving to Assess), and returns success message.
    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 }] };
    }
  • Validation helper specific to transitions from Decide realm. Allows backward move to Assess for re-evaluation and enforces rules for moving to Do (requires context and future due date).
    private validateFromDecide(item: any, targetRealmId: number, itemType: string): {valid: boolean, reason: string} {
      switch (targetRealmId) {
        case REALM_DO_ID: // Decide -> Do
          // Must have context and due date to move to Do
          if (!item.contextRecordName) {
            return { valid: false, reason: `${itemType} must have a context assigned before moving to Do realm` };
          }
          if (!item.endDate) {
            return { valid: false, reason: `${itemType} must have a due date set before moving to Do realm` };
          }
          
          // Check if due date is in the future (not stalled)
          const now = new Date();
          const dueDate = new Date(item.endDate);
          if (dueDate < now) {
            return { 
              valid: false, 
              reason: `${itemType} has a past due date (${dueDate.toLocaleDateString()}) - update due date or move back to Assess` 
            };
          }
          
          return { valid: true, reason: `${itemType} ready for Do realm - context and future due date set` };
        
        case REALM_ASSESS_ID: // Decide -> Assess (backward)
          // Allow backward movement for re-evaluation
          return { 
            valid: true, 
            reason: `${itemType} moved back to Assess realm for re-evaluation - context and due date will be cleared` 
          };
        
        case REALM_DECIDE_ID: // Decide -> Decide
          return { valid: false, reason: `${itemType} is already in Decide realm` };
        
        default:
          return { valid: false, reason: `Invalid target realm ID: ${targetRealmId}` };
      }
    }
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 action ('Move') but doesn't explain what 'Move' entails (e.g., does it modify task status, trigger notifications, or have side effects?), required permissions, error conditions, or response format. For a mutation tool with zero annotation coverage, this leaves critical behavioral traits unspecified.

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, direct sentence with zero wasted words. It front-loads the core action ('Move task') and efficiently specifies the realms involved. Every element earns its place, making it easy to parse quickly.

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 complexity (a mutation tool with no annotations and no output schema), the description is incomplete. It lacks details on behavioral traits (e.g., what 'Move' means operationally), error handling, and what happens post-move. While the schema covers the single parameter, the overall context for safe and effective use is insufficient.

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 adds no parameter-specific information beyond implying that the task must be in the Decide realm. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description doesn't enhance parameter understanding.

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 source ('Decide realm') and destination ('Assess realm'). It distinguishes this tool from other move operations like 'decide_move_task_to_do' by specifying the target realm. However, it doesn't fully differentiate from 'moveToRealm' (a sibling tool), which might handle similar functionality more generically.

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 (e.g., the task must be in the Decide realm), exclusions, or comparisons to sibling tools like 'moveToRealm' or other realm-specific moves. The agent must infer usage from the name and 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