Skip to main content
Glama
davidorex

Project Handoffs MCP Server

by davidorex

create_next_step

Adds a new task or milestone to a project with title, description, priority level, and optional dependencies to maintain organized workflow progression.

Instructions

Create a new next step in a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesProject identifier
titleYesBrief title of the next step
descriptionYesDetailed description of work
priorityYesImplementation priority level
parentStepIdNoID of parent step if this is a substep
dependenciesNoIDs of steps that must be completed first

Implementation Reference

  • Core handler function in ProjectManager that executes the create_next_step logic: validates template, checks dependencies, generates ID/timestamps, persists to project data file.
    async createNextStep(projectId: string, step: Omit<NextStep, 'id' | 'created' | 'lastModified'>): Promise<NextStep> {
      this.validateTemplate('next_step', step);
      
      const data = await this.loadProjectData(projectId);
      
      const newStep: NextStep = {
        ...step,
        id: `step_${Date.now()}`,
        created: new Date().toISOString(),
        lastModified: new Date().toISOString(),
      };
    
      // Validate dependencies exist
      if (step.dependencies?.length) {
        const missingDeps = step.dependencies.filter(
          depId => !data.nextSteps.some(s => s.id === depId)
        );
        if (missingDeps.length > 0) {
          throw new ProjectError(`Dependencies not found: ${missingDeps.join(', ')}`, projectId);
        }
      }
    
      data.nextSteps.push(newStep);
      await this.saveProjectData(projectId, data);
      return newStep;
    }
  • Input schema definition for the create_next_step tool, specifying parameters, types, descriptions, and required fields.
    inputSchema: {
      type: "object",
      properties: {
        projectId: { type: "string", description: "Project identifier" },
        title: { type: "string", description: "Brief title of the next step" },
        description: { type: "string", description: "Detailed description of work" },
        priority: { 
          type: "string",
          enum: ["core-critical", "full-required", "enhancement"],
          description: "Implementation priority level"
        },
        parentStepId: { type: "string", description: "ID of parent step if this is a substep" },
        dependencies: { 
          type: "array",
          items: { type: "string" },
          description: "IDs of steps that must be completed first"
        }
      },
      required: ["projectId", "title", "description", "priority"]
    }
  • src/index.ts:448-466 (registration)
    MCP CallToolRequest handler case that processes arguments and invokes the createNextStep method, returning the result.
    case "create_next_step":
      const step = await projectManager.createNextStep(
        args.projectId as string,
        {
          projectId: args.projectId as string,
          title: args.title as string,
          description: args.description as string,
          priority: args.priority as NextStep['priority'],
          parentStepId: args.parentStepId as string,
          dependencies: args.dependencies as string[] || [],
          status: 'open'
        }
      );
      return {
        content: [{
          type: "text",
          text: JSON.stringify(step, null, 2)
        }]
      };
  • src/index.ts:322-344 (registration)
    Tool registration in ListToolsResponse, defining name, description, and input schema for create_next_step.
    {
      name: "create_next_step",
      description: "Create a new next step in a project",
      inputSchema: {
        type: "object",
        properties: {
          projectId: { type: "string", description: "Project identifier" },
          title: { type: "string", description: "Brief title of the next step" },
          description: { type: "string", description: "Detailed description of work" },
          priority: { 
            type: "string",
            enum: ["core-critical", "full-required", "enhancement"],
            description: "Implementation priority level"
          },
          parentStepId: { type: "string", description: "ID of parent step if this is a substep" },
          dependencies: { 
            type: "array",
            items: { type: "string" },
            description: "IDs of steps that must be completed first"
          }
        },
        required: ["projectId", "title", "description", "priority"]
      }
  • Helper method called by createNextStep to validate input against HANDOFF_TEMPLATES for 'next_step'.
    private validateTemplate(type: string, data: Record<string, any>): void {
      const template = HANDOFF_TEMPLATES[type];
      if (!template) return; // Non-templated types are valid
    
      const missingFields = template.fields
        .filter(field => field.required)
        .filter(field => {
          const fieldName = field.name.toLowerCase().replace(/\s+/g, '_');
          return !data[fieldName] && !data[field.name];
        });
    
      if (missingFields.length > 0) {
        throw new ProjectError(
          `Missing required fields for ${type}: ${missingFields.map(f => f.name).join(', ')}`,
          data.projectId || 'validation'
        );
      }
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it 'creates' without disclosing behavioral traits like permissions needed, whether it's idempotent, error handling, or what happens on success. It mentions the action but lacks critical operational details 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 zero waste, front-loading the core purpose. Every word earns its place, making it highly concise and well-structured.

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 6 parameters, no annotations, and no output schema, the description is incomplete. It lacks context on what the tool returns, error conditions, or how it integrates with sibling tools, leaving significant gaps for agent understanding.

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 fully documents all 6 parameters. The description adds no additional meaning beyond the schema, such as explaining relationships between parameters like 'parentStepId' and 'dependencies'. Baseline 3 is appropriate as 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 ('create') and resource ('new next step in a project'), which is specific and unambiguous. However, it doesn't differentiate from sibling tools like 'create_project' or 'create_handoff' beyond the resource type, missing explicit sibling distinction.

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 like 'create_project' or 'create_handoff'. The description implies usage for adding steps to existing projects but lacks explicit context, prerequisites, or exclusions.

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/davidorex/project-handoffs'

If you have feedback or need assistance with the MCP directory API, please join our Discord server