Skip to main content
Glama
davidorex

Project Handoffs MCP Server

by davidorex

create_project

Initiate a new project to track AI session handoffs and manage workflow transitions, enabling organized task prioritization and progress monitoring.

Instructions

Create a new project for tracking AI session handoffs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesProject name
descriptionYesProject description

Implementation Reference

  • Core handler function in ProjectManager class that creates a new project: generates sanitized ID from name, checks for existing projects, creates ProjectMetadata, appends to projects list, saves metadata, initializes empty project data file, and returns the new project metadata.
    async createProject(name: string, description: string): Promise<ProjectMetadata> {
      const projects = await this.loadMetadata();
      const id = name.toLowerCase().replace(/[^a-z0-9]/g, '_');
      
      if (projects.some(p => p.id === id)) {
        throw new ProjectError('Project with this name already exists', id);
      }
    
      const newProject: ProjectMetadata = {
        id,
        name,
        description,
        created: new Date().toISOString(),
        lastAccessed: new Date().toISOString()
      };
    
      projects.push(newProject);
      await this.saveMetadata(projects);
      await this.saveProjectData(id, { nextSteps: [], workingSessions: [], handoffs: [] });
      
      return newProject;
    }
  • Input schema definition for the create_project tool, requiring 'name' and 'description' as strings.
    inputSchema: {
      type: "object",
      properties: {
        name: { type: "string", description: "Project name" },
        description: { type: "string", description: "Project description" }
      },
      required: ["name", "description"]
    }
  • src/index.ts:299-310 (registration)
    Tool registration in the list_tools response, defining name, description, and input schema for create_project.
    {
      name: "create_project",
      description: "Create a new project for tracking AI session handoffs",
      inputSchema: {
        type: "object",
        properties: {
          name: { type: "string", description: "Project name" },
          description: { type: "string", description: "Project description" }
        },
        required: ["name", "description"]
      }
    },
  • src/index.ts:427-437 (registration)
    Tool dispatch/registration in the CallToolRequestSchema handler: extracts arguments, calls the createProject handler, and returns result as JSON text content.
    case "create_project":
      const project = await projectManager.createProject(
        args.name as string,
        args.description as string
      );
      return {
        content: [{
          type: "text",
          text: JSON.stringify(project, null, 2)
        }]
      };
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Create' implies a write/mutation operation, the description doesn't specify permissions required, whether the operation is idempotent, what happens on conflicts, or what the response includes (e.g., project ID). 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 directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, with every word earning its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (a simple creation operation with 2 parameters), 100% schema coverage, and no output schema, the description is minimally complete. It states what the tool does but lacks behavioral details and usage context, which are important for a mutation tool without annotations. It's adequate but has clear gaps.

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 documents both parameters ('name' and 'description') adequately. The description doesn't add any meaning beyond what the schema provides, such as constraints, examples, or formatting details. Baseline 3 is appropriate when 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 verb ('Create') and resource ('new project'), and specifies the purpose ('for tracking AI session handoffs'). However, it doesn't differentiate from sibling tools like 'create_handoff' or 'create_next_step', which appear related to the same domain but have different functions.

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 like 'create_handoff' or 'create_next_step', nor does it mention prerequisites, dependencies, or exclusions. It merely states what the tool does without contextual usage information.

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