Skip to main content
Glama
dragosroua

addTaskManager MCP Server

by dragosroua

decide_move_project_to_do

Move a project from the Decide realm to the Do realm to mark it ready for execution within the ADD framework.

Instructions

Move project to Do realm from Decide realm.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectRecordNameYesProject record name

Implementation Reference

  • src/index.ts:724-726 (registration)
    Registration and dispatch for the 'decide_move_project_to_do' tool in the CallToolRequestSchema switch statement, calling the moveProjectToRealm handler.
    case 'decide_move_project_to_do':
      this.validateArgs(args, ['projectRecordName']);
      return await this.moveProjectToRealm(args.projectRecordName, 'do');
  • Primary handler function for 'decide_move_project_to_do' tool. Validates the realm transition for the project and delegates to the generic moveItemToRealm method if valid.
    private async moveProjectToRealm(projectRecordName: string, targetRealm: string) {
      // Add validation before moving
      const validationResult = await this.validateRealmTransition(projectRecordName, 'Project', targetRealm as RealmString);
      if (!validationResult.valid) {
        throw new McpError(ErrorCode.InvalidParams, validationResult.reason);
      }
      return this.moveItemToRealm(projectRecordName, 'Project', targetRealm as RealmString);
    }
  • Core helper method that performs the realm move operation for projects or tasks, currently implemented as a mock that returns a success message (production would update CloudKit).
    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 that validates ADD framework realm transition rules before allowing project move from Decide to Do, ensuring context and future due date are set.
    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}` };
      }
    }
  • Tool registration including name, description, and input schema definition for 'decide_move_project_to_do' in ListTools response.
    name: 'decide_move_project_to_do',
    description: 'Move project to Do realm from Decide realm.',
    inputSchema: {
      type: 'object',
      properties: {
        projectRecordName: { type: 'string', description: 'Project record name' }
      },
      required: ['projectRecordName']
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the action is a move operation, implying mutation, but lacks details on permissions required, side effects (e.g., what happens to associated tasks), reversibility, or error conditions. This is a significant gap for a mutation tool with zero annotation coverage.

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 is front-loaded with the core action and resource, 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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks behavioral details (e.g., effects, permissions) and output information, which are critical for an agent to use it correctly. The high schema coverage helps minimally, but overall context 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?

Schema description coverage is 100%, with the single parameter 'projectRecordName' documented in the schema. The description adds no additional parameter information beyond implying the project is moved, so it meets the baseline of 3 where the schema does the heavy lifting.

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 ('project'), specifying the source realm ('Decide') and destination realm ('Do'). It distinguishes from siblings like 'decide_move_project_to_assess_from_decide' by specifying the destination, though it doesn't explicitly contrast with 'moveToRealm' which might be a generic version.

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., project must be in Decide realm), exclusions, or compare with similar tools like 'moveToRealm' or 'decide_move_project_to_assess_from_decide', leaving the agent to infer usage context.

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