Skip to main content
Glama
davidorex

Project Handoffs MCP Server

by davidorex

create_handoff

Document completed work and current project state to facilitate team handoffs, including code status, unresolved issues, and next steps.

Instructions

Complete a working session with handoff details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesProject identifier
sessionIdYesWorking session ID
completedWorkYesSummary of completed work
codeStateYesCurrent state of codebase
environmentStateYesDevelopment environment state
unresolvedIssuesNoList of unresolved issues
newNextStepsNoList of new next steps identified

Implementation Reference

  • Core handler function in ProjectManager that executes the create_handoff logic: validates template, loads project data, verifies session/step, updates statuses, creates and saves the handoff object.
    async createHandoff(
      projectId: string,
      sessionId: string,
      handoff: Omit<Handoff, 'id' | 'sessionId' | 'timestamp'>
    ): Promise<Handoff> {
      this.validateTemplate('handoff', handoff);
      
      const data = await this.loadProjectData(projectId);
      
      const session = data.workingSessions.find(s => s.id === sessionId);
      if (!session) {
        throw new ProjectError(`Session not found: ${sessionId}`, projectId);
      }
      if (session.endTime) {
        throw new ProjectError(`Session already ended: ${sessionId}`, projectId);
      }
    
      const step = data.nextSteps.find(s => s.id === session.nextStepId);
      if (!step) {
        throw new ProjectError(`Associated next step not found: ${session.nextStepId}`, projectId);
      }
    
      session.endTime = new Date().toISOString();
      step.status = 'completed';
      step.lastModified = new Date().toISOString();
    
      const newHandoff: Handoff = {
        ...handoff,
        id: `handoff_${Date.now()}`,
        sessionId,
        timestamp: new Date().toISOString()
      };
    
      data.handoffs.push(newHandoff);
      await this.saveProjectData(projectId, data);
      return newHandoff;
    }
  • Input schema definition for the create_handoff tool, specifying properties, types, descriptions, and required fields.
    inputSchema: {
      type: "object",
      properties: {
        projectId: { type: "string", description: "Project identifier" },
        sessionId: { type: "string", description: "Working session ID" },
        completedWork: { type: "string", description: "Summary of completed work" },
        codeState: { type: "string", description: "Current state of codebase" },
        environmentState: { type: "string", description: "Development environment state" },
        unresolvedIssues: {
          type: "array",
          items: { type: "string" },
          description: "List of unresolved issues"
        },
        newNextSteps: {
          type: "array",
          items: { type: "string" },
          description: "List of new next steps identified"
        }
      },
      required: ["projectId", "sessionId", "completedWork", "codeState", "environmentState"]
    }
  • src/index.ts:358-382 (registration)
    Tool registration in the ListTools response, defining name, description, and input schema for create_handoff.
    {
      name: "create_handoff",
      description: "Complete a working session with handoff details",
      inputSchema: {
        type: "object",
        properties: {
          projectId: { type: "string", description: "Project identifier" },
          sessionId: { type: "string", description: "Working session ID" },
          completedWork: { type: "string", description: "Summary of completed work" },
          codeState: { type: "string", description: "Current state of codebase" },
          environmentState: { type: "string", description: "Development environment state" },
          unresolvedIssues: {
            type: "array",
            items: { type: "string" },
            description: "List of unresolved issues"
          },
          newNextSteps: {
            type: "array",
            items: { type: "string" },
            description: "List of new next steps identified"
          }
        },
        required: ["projectId", "sessionId", "completedWork", "codeState", "environmentState"]
      }
    },
  • MCP CallToolRequest handler case that parses arguments and delegates to ProjectManager.createHandoff, returning the result as JSON text content.
    case "create_handoff":
      const handoff = await projectManager.createHandoff(
        args.projectId as string,
        args.sessionId as string,
        {
          completedWork: args.completedWork as string,
          codeState: args.codeState as string,
          environmentState: args.environmentState as string,
          unresolvedIssues: args.unresolvedIssues as string[] || [],
          newNextSteps: args.newNextSteps as string[] || []
        }
      );
      return {
        content: [{
          type: "text",
          text: JSON.stringify(handoff, null, 2)
        }]
      };
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 implies a write operation ('complete') but doesn't specify permissions needed, whether the action is reversible, or what happens to the session post-completion. This is inadequate 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's action. It's front-loaded and wastes no words, though it could be slightly more specific without losing conciseness.

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 7 parameters, no annotations, and no output schema, the description is incomplete. It lacks behavioral details (e.g., effects, permissions), usage context, and output expectations, making it insufficient for safe and effective use.

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 7 parameters. The description adds no parameter-specific information beyond what's in the schema, such as examples or constraints. Baseline 3 is appropriate when the schema handles all parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool 'Complete[s] a working session with handoff details', which provides a clear verb ('complete') and resource ('working session'). However, it doesn't specify what 'handoff details' entail or distinguish this tool from sibling tools like 'start_working_session' or 'create_next_step', leaving the purpose somewhat vague.

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 offers no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., must have an active session), exclusions, or relationships to sibling tools like 'start_working_session' or 'create_next_step', leaving usage unclear.

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