Skip to main content
Glama

project_create

Create a new project container to organize work in a structured database, enabling AI agents to track epics, tasks, and decisions across sessions.

Instructions

Create a new project. Projects are the top-level container for all work.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesProject name
descriptionNoProject description
statusNoProject statusactive
tagsNoTags for categorization

Implementation Reference

  • The handler function that executes the logic to create a new project in the database.
    function handleProjectCreate(args: Record<string, unknown>) {
      const db = getDb();
      const name = args.name as string;
      const description = (args.description as string) ?? null;
      const status = (args.status as string) ?? 'active';
      const tags = JSON.stringify((args.tags as string[]) ?? []);
    
      const project = db
        .prepare(
          'INSERT INTO projects (name, description, status, tags) VALUES (?, ?, ?, ?) RETURNING *'
        )
        .get(name, description, status, tags);
    
      const row = project as Record<string, unknown>;
      logActivity(db, 'project', row.id as number, 'created', null, null, null, `Project '${name}' created`);
    
      return project;
    }
  • The MCP tool definition and schema for the project_create tool.
    {
      name: 'project_create',
      description: 'Create a new project. Projects are the top-level container for all work.',
      annotations: { title: 'Create Project', readOnlyHint: false, destructiveHint: false, idempotentHint: false, openWorldHint: false },
      inputSchema: {
        type: 'object',
        properties: {
          name: { type: 'string', description: 'Project name' },
          description: { type: 'string', description: 'Project description' },
          status: {
            type: 'string',
            enum: ['active', 'on_hold', 'completed', 'archived'],
            default: 'active',
            description: 'Project status',
          },
          tags: {
            type: 'array',
            items: { type: 'string' },
            description: 'Tags for categorization',
          },
        },
        required: ['name'],
      },
    },
  • Registration of the project_create handler within the tools map.
    export const handlers: Record<string, ToolHandler> = {
      project_create: handleProjectCreate,
Behavior4/5

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

Annotations provide readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, covering safety and idempotency. The description adds context about projects being 'top-level container for all work', which helps the agent understand the organizational role and potential impact, though it doesn't detail permissions, rate limits, or creation constraints beyond what annotations imply.

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 two concise sentences with zero waste: the first states the core action, and the second adds valuable context about projects' role. It's front-loaded with the primary purpose and efficiently structured.

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

Completeness4/5

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

For a creation tool with good annotations (covering safety and idempotency) and full schema coverage, the description is mostly complete. It lacks output details (no output schema) and doesn't specify creation constraints like duplicate handling, but the context about top-level containers helps. Given the complexity and annotation richness, it's adequate with minor 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%, with clear descriptions for all parameters including enum values for status. The description doesn't add any parameter-specific semantics beyond the schema, such as naming conventions or tag usage guidelines, so it meets the baseline of 3 where schema does the heavy lifting.

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

Purpose5/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 distinguishes from siblings like project_list and project_update by specifying it's for creation rather than listing or updating. The additional context about projects being 'top-level container for all work' helps differentiate from other container-like tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when a new project is needed, but doesn't explicitly state when to use this vs alternatives like template_apply for project creation from templates, or when not to use it (e.g., for updating existing projects). It mentions projects as top-level containers, which provides some contextual guidance but lacks explicit alternatives 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/spranab/saga-mcp'

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