Skip to main content
Glama
dragosroua

addTaskManager MCP Server

by dragosroua

decide_move_project_to_assess_from_decide

Move a project from the Decide realm to the Assess realm to enable content creation and editing within the ADD framework.

Instructions

Move project to Assess realm from Decide realm.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectRecordNameYesProject record name

Implementation Reference

  • src/index.ts:510-520 (registration)
    Tool registration in the list of tools returned by ListToolsRequestSchema, defining name, description, and input schema.
    {
      name: 'decide_move_project_to_assess_from_decide',
      description: 'Move project to Assess realm from Decide realm.',
      inputSchema: {
        type: 'object',
        properties: {
          projectRecordName: { type: 'string', description: 'Project record name' }
        },
        required: ['projectRecordName']
      }
    },
  • Input schema specifying the required projectRecordName parameter.
    inputSchema: {
      type: 'object',
      properties: {
        projectRecordName: { type: 'string', description: 'Project record name' }
      },
      required: ['projectRecordName']
    }
  • Dispatch handler case in CallToolRequestSchema that validates arguments and calls the moveProjectToRealm method.
    case 'decide_move_project_to_assess_from_decide':
      this.validateArgs(args, ['projectRecordName']);
      return await this.moveProjectToRealm(args.projectRecordName, 'assess');
  • Primary handler function implementing the tool logic: validates realm transition and delegates to 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 helper implementing the realm change, including realm-specific rules like clearing context and dates when moving to Assess.
    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. It states the action is a 'move' (implying mutation), but doesn't describe what this entails—whether it changes project status, affects associated tasks, requires permissions, or has side effects. This leaves significant gaps 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 with no wasted words. It front-loads the key action and is appropriately sized for a simple tool with one parameter.

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 incomplete. It lacks details on behavioral implications, success/failure outcomes, and how it fits into the broader workflow with siblings, leaving the agent with insufficient context.

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 schema description coverage is 100%, with the parameter 'projectRecordName' clearly documented in the schema. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline of 3 for high schema coverage.

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 ('from Decide realm') and destination ('to Assess realm'). It distinguishes from some siblings like 'decide_move_project_to_do' by specifying the target realm, but doesn't explicitly differentiate from similar tools like 'moveToRealm' or '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 doesn't mention prerequisites, conditions for moving projects, or when to choose this over other tools like 'moveToRealm' or 'assess_archive_project_to_collection'.

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