Skip to main content
Glama
dragosroua

addTaskManager MCP Server

by dragosroua

moveToRealm

Transfer tasks or projects between ADD framework realms (Assess, Decide, Do) to manage workflow stages and enforce realm-specific actions like editing, scheduling, or completion.

Instructions

Move a task or project to a specific realm.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemRecordNameYesRecord name of the task or project to move
itemTypeYesType of item to move
realmIdYesTarget realm (assess=1, decide=2, do=3)

Implementation Reference

  • Schema definition for the moveToRealm tool, including input parameters and description. Part of the tools list returned by listTools.
      name: 'moveToRealm',
      description: 'Move a task or project to a specific realm.',
      inputSchema: {
        type: 'object',
        properties: {
          itemRecordName: { type: 'string', description: 'Record name of the task or project to move' },
          itemType: { type: 'string', enum: ['Task', 'Project'], description: 'Type of item to move' },
          realmId: { type: 'string', enum: ['assess', 'decide', 'do'], description: 'Target realm (assess=1, decide=2, do=3)' }
        },
        required: ['itemRecordName', 'itemType', 'realmId']
      }
    },
  • Main handler for moveToRealm tool in the CallToolRequestSchema switch statement. Validates args and dispatches to task/project specific move functions.
      if (args.itemType === 'Task') {
        return await this.moveTaskToRealm(args.itemRecordName, args.realmId);
      } else if (args.itemType === 'Project') {
        return await this.moveProjectToRealm(args.itemRecordName, args.realmId);
      } else {
        throw new McpError(ErrorCode.InvalidParams, 'itemType must be Task or Project');
      }
    case 'get_collections':
      return await this.getCollections();
  • Task-specific handler that validates realm transition before calling generic 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);
    }
  • Project-specific handler that validates realm transition before calling generic moveItemToRealm.
    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 implementation logic for moving an item to a target realm, including realm-specific message and mock update.
    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 }] };
    }
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. While 'Move' implies a mutation operation, the description doesn't address important behavioral aspects: whether this requires specific permissions, whether the move is reversible, what happens to dependent items, or what the response looks like. For a mutation tool with zero annotation coverage, this is a significant gap.

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 clearly states the tool's purpose with zero wasted words. It's appropriately sized for a simple operation and front-loads the essential information.

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?

For a mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address behavioral implications, error conditions, or what happens after the move operation. Given the complexity of moving items between realms (which likely affects workflow state), more context about the operation's effects and constraints would be needed.

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%, so the schema already fully documents all three parameters with their types, enums, and descriptions. The description doesn't add any parameter-specific information beyond what's in the schema, such as explaining the relationship between parameters or providing usage examples. The baseline score of 3 reflects adequate coverage through the schema alone.

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 target resources ('a task or project to a specific realm'), providing a specific verb+resource combination. However, it doesn't explicitly distinguish this tool from sibling tools like 'decide_move_project_to_assess_from_decide' or 'decide_move_task_to_assess_from_decide', which appear to perform similar realm-moving operations.

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. With multiple sibling tools that appear to handle realm transitions (e.g., 'decide_move_project_to_assess_from_decide', 'decide_move_task_to_assess_from_decide'), there's no indication of when this general 'moveToRealm' tool should be preferred over those more specific tools.

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